The Number #1 rated app

draw.io has a number of impressive feats, including:

• 99% of the Fortune 500 use our app;
• We have more installs and more users than any other Atlassian app;
• We are the #1 rated diagramming app on the Atlassian Marketplace for Confluence and Jira.

The underlying reason for this is that people know and trust our app: they know that their data is in safe hands, and expect a versatile tool that delivers, as well as high-quality support with their diagramming and visualization needs.

If you’re thinking about switching tools and are looking for a solution that can do it all, then read on! Below, we take a look at why so many users choose draw.io in Confluence and Jira over other diagramming tools that are not in the Atlassian ecosystem:

Visualize in your single source of truth

The primary reason that many companies use Confluence and Jira is not just because they are powerful knowledge and project management tools, but because they abide by high security standards. For organizations looking to ensure their data remains secure, and to maintain audit trails for compliance purposes, Confluence and Jira offer the perfect solution.

When using the draw.io app, your diagram data is stored as attachments within Confluence/Jira. This keeps all your diagrams secure, embedded within your single source of truth. It also saves you time and money in the long run by eliminating the pain point of having multiple apps to fulfill a purpose.

If you want to visualize within your Confluence/Jira space, and keep these visualizations within the Confluence documentation or Jira issue that they belong to, you can. Your colleagues will thank you too, as it cuts out the frustration of having to locate diagrams stored elsewhere on other platforms or webpages.

Choose to create a new diagram from scratch, or embed existing diagrams that you have created in other Confluence pages.

Choose to create a new diagram, or embed an existing one

If you embed an existing diagram in multiple Confluence pages and want to make changes, you will be taken to the original version of the diagram, and any changes will automatically apply to all the other embedded versions.

Clicking on the Go to containing page icon will open the Confluence page containing the original diagram in a new window

Secure diagramming

A big concern for users is ensuring their diagramming data is safe. For small and large enterprises alike, company data is precious. The risk of data mismanagement and security breaches increases the more tools you use. Therefore, the reassurance that their number one visualization tool is keeping their diagrams and whiteboards safe is why so many users choose draw.io.

We conform to the highest enterprise-grade security and privacy standards, so users can rest assured that their data is in safe hands. When you work on a draw.io diagram in Confluence/Jira, Data Center or Cloud, you have full control over your data, as this is stored as page attachments within the Confluence page or Jira issue that the diagram or whiteboard is embedded in.

Revision history

This is also a powerful feature for your audits. In addition to Confluence’s in-built page history, there is versioning in the draw.io app itself, enabling you to see exactly who made changes and when. You are then able to revert diagrams if someone has made unwanted changes to a diagram, without affecting the Confluence page the diagram is embedded in.

Revision history in draw.io

Access control

Another problem users face is controlling who they share diagrams with. Often, the platform they are using provides an “all-or-nothing” solution: either everyone has access, or no one does.

People want full control over their diagrams and the information that accompanies them. Especially on things like Confluence pages for example, which contain sensitive information that not everyone in the company requires access to.

Fortunately, with your draw.io diagrams stored on specific Confluence pages, you are able to control on a granular level who has access to which information. Choose who has editing access, or who only has viewing access, to the relevant Confluence pages and embedded diagrams – this can be done on an individual or team-wide level.

Control who has view/edit access to a specific Confluence page

Diagramming or whiteboarding? Why not both?

With draw.io, you don’t have to choose between diagramming or whiteboarding capabilities. When you use draw.io in Confluence/Jira, you have diagramming AND whiteboarding, all in one app. You have access to all the same features in both.

This suits teams across the board, from engineering and software development, right through to marketing and HR. Each individual in every team can use the editor that best suits them: the original diagram editor or our whiteboard editor, depending on their visualization needs and which interface they prefer.

The “classic” draw.io diagram editor

The whiteboard editor

Search for text within diagrams

Easily find your diagrams using Atlassian’s in-built Confluence Search function. Text you add to your diagrams is indexed and searchable, so you can use the Confluence search bar to locate diagrams using specific search terms.

Tip: use the advanced search and filter by Type > draw.io Diagrams to bring up diagram-related searches only.

Search for text in your diagrams using the Confluence search bar

Cloud-specific advantages

Data residency:

Atlassian has implemented data residency options for Confluence and Jira Cloud. This means that all of the primary data stored in your Confluence and/or Jira instance will reside on servers in your chosen region.

For more information, see our blogpost, Introducing Data Governance in our Standard draw.io plan for Confluence Cloud.

Lockdown data:

If you want to prevent all data traffic apart from that between your browser and your Atlassian Cloud server, you can use the Lockdown function in the draw.io configuration to do so.

Invite guests to Confluence:

Working with users outside of your organization? You can invite up to 5 guests per paying user to collaborate in Confluence.

For more information, see Invite guests to use draw.io with you in Confluence Cloud.

Collaborative editing:

Collaborate on diagrams with your colleagues synchronously. Any changes made by multiple teammates are saved automatically. “@-mention” your teammates on Confluence pages containing your diagrams, to add a comment and notify them.

Notify your teammates in Confluence pages using “@-mention”

Data Center-specific advantages

Everything behind your firewall:

If you opt for Data Center, your data is stored in a self-managed environment, behind your firewall. This gives you full control over everything like security controls, update releases, and infrastructure choices.

Control over updates:

You have control over what happens when, as you are responsible for manually installing any maintenance and version upgrades.

The one tool for every team

draw.io’s standing in the Atlassian Marketplace is very much built on the trust of its users. If you are looking for a solution for your company that:

• stores your diagrams and whiteboards within your single source of truth (Confluence or Jira), without needing to leave the platform you’re working in to access these;
• is a versatile tool that allows you to diagram, whiteboard, and visualize the way that you want;
• offers tight security, protecting your diagramming data while allowing you to collaborate with specific members in and outside of your organization;

then draw.io is the solution for you and your team!

Want to try draw.io for free?

Making peace with Atlassian Server end of support

To commemorate Atlassian Server coming to an end, and all the years it has been a steadfast companion for many Confluence and Jira users, we decided to build a Zen garden, in its memory. Support for Server products will end on February 15, 2024 – find out what this means for you.

Server has been instrumental for all sorts of companies from non-profits to global tech giants for decades, offering them an on-premise, secure solution to document and share knowledge, boost productivity, and perform at scale. It’s transformed how we build, deploy, and manage applications today. For Atlassian specifically, it’s laid the foundations to develop their Cloud-first strategy as well as its Data Center provision.

Getting started

With end of support taking place this week, it felt like an appropriate time to celebrate the importance of Server with a memorial. The Zen garden is situated in our office here in Wiesbaden, Germany. It will serve not only as a long-lasting dedication to Server, but also as a space for people to pause and reflect, and be an area that everyone can enjoy for their own reasons.

Rather fortuitously, the Zen garden build coincided with a visit from a couple of our colleagues from the US and Canada, who were also willing to get their hands dirty and lend a helping hand!

We learned a lot along the way of building the garden. Below, we take a look at the hard work that went into the planning and building, and what our key takeaways were from the experience.

The steps involved

Our first step was to work with our Space Creator Team to find the right space for the Zen garden. The result was a corner of the roof terrace, approximately 10 square feet in size, that would fit the bill.

Finding a place for the Zen garden

The next step was deciding on the right plants and decoration for the garden. Of course color, maintenance, and how much the plants will grow were all factors considered – but most importantly – which will thrive in the variable and inclement German weather conditions! We also decided on a lantern ornament in keeping with the overall theme, and to tie the garden together.

The space we used had very specific dimensions in a right-angled alcove, so to visualize our Zen garden we turned to the one tool that could serve our purposes – our very own draw.io!

Planning the Zen garden layout and features in draw.io

With the location decided and a blueprint of the garden, we turned to our trusty Subject Matter Expert, Basti who, it turns out, is also a subject expert on Zen gardens! He took a trip to the DIY store to purchase the supplies we would need.

Our more practical team members then got building the Zen garden foundations.

A Ryoba saw seemed very fitting for the occasion!

Once the foundations were down and the gravel and soil added, it was time to roll up our sleeves and get potting!

As members of the team potted the plants, it was interesting to see who in the team seemed to be more experienced with gardening – some would carefully break up the roots and embed the plant deep into the soil; others just popped the plant straight into the ground!

Putting our new-found friend, “Drake”, to good use

The final touches

With the Zen garden complete, it was time to take stock and see how our hard work had paid off.

Our Social Media Coordinator, Charis, took the final video footage of the finished Zen garden, which felt uncannily like some kind of technological baptism for the garden.

The completed Zen garden

A time to pause and reflect

We learned a number of things along the way: the value of hard work, and the pride we can all feel in the finished piece from the fruits of our labor. That teamwork makes things go much more smoothly, and lastly, that the Zen garden is an ongoing process that will require regular upkeep to remain pristine and decluttered.

There are certainly parallels to be drawn between building a Zen garden and ensuring a smooth migration: taking stock of the current landscape; identifying which apps are still useful and which need a good pruning; and performing a pre-migration data cleanup to ensure you’re not carrying any excess baggage with you. All of this leaves your new Confluence/Jira instance decluttered and ready-to-go, and regular maintenance will ensure it stays that way.

Some personal takeaways:

• It’s better to plan where any small potted plants will go, before actually planting them.
• Fargesia is very heavy.
• Lastly: It’s rather cold in Germany – perhaps it’s better to build a Zen garden in summer!

Looking ahead to the future

Four years ago, Atlassian announced the discontinuation of Server products. For companies big and small, we know people have done amazing things with Server-based tools, and Atlassian’s products have laid the foundation for much of the SaaS products we use today.

Atlassian’s pledges for Server, i.e. a secure solution to document and share knowledge, boost productivity, and perform at scale, still persist today for Atlassian Cloud and Data Center. These pledges are also very much at the heart of draw.io: we offer live, real-time collaboration on diagrams (in Cloud) to help teams work together effectively. Our enterprise-grade security and privacy standards mean your diagrams are always secure – we don’t see or track your use of draw.io.

As we say farewell to Server, we look forward to seeing how lives will be improved with the new era of Cloud and Data Center.

If you are migrating from Server and wish to find out more about your options, please see our related blogpost: What does the future of draw.io look like after Server EOL?

Grow with draw.io

Want to dive deeper into the world of draw.io? Access our linktr.ee page to follow us on social media and learn how others use draw.io, as well as pick up some helpful tips and tricks.

Unpacking the right information

There’s a lot to think about when it comes to migrating deployments, but fortunately, the process is generally straightforward. The key is to be well-prepared and know what to expect.

In this blogpost, we’ll be looking at the different options for changing deployments: from on-premise (Server or Data Center) to Cloud, or from one Cloud instance to another.

The good news is, whichever deployments you are migrating from and to, you won’t need to worry about the draw.io diagrams you have previously created. These are stored as attachments in your Confluence or Jira instance, and so when migrating they will be unaffected. There are a couple of things to be aware of that will make migrating much smoother, so be sure to check out the respective Confluence and Jira sections below!

What’s more, our migration steps do not involve migrating any data. Your draw.io data stays entirely in your browser; it is stored securely and exclusively in your Confluence or Jira instance, and only in Atlassian products and services.

Migrating from on-premise to Cloud

Server

We are part of the Atlassian Dual Licensing program. This program has been extended to also include Server, provided that users purchase a subscription before February 15, 2024. This program entitles users to receive ongoing Server support until February 15 2025, provided that they purchase a draw.io for Confluence Cloud subscription. More details can be found here.

Please note: we are going to provide draw.io support for all Confluence Server versions 8.5 and above only.

So we recommend that you update to Confluence Server 8.5 and above and the corresponding draw.io version, which is 12.2.1.

Recommended: Perform a test migration

When migrating from on-premise to Cloud, your existing diagrams will be deleted and replaced with a Cloud-compatible format.

This is a one-way operation – the changes cannot be undone. It is therefore strongly recommended that you perform the operation in a test environment first, to identify any issues that may come up before you migrate your diagrams. Fortunately, Confluence Server and Data Center both allow you to set up a sandbox environment that mirrors your live deployment, at no extra cost.

Confluence

Confluence stores your draw.io diagrams as page attachments. When migrating Confluence, the page attachments transfer across, and so your diagrams therefore automatically migrate as well.

Migrating from on-premise to Cloud

Migrating from on-premise to Cloud is a great way to keep all your information in Confluence centralized and instantly accessible to the right people who need to view or edit.

When migrating from Confluence on-premise, you can use our updated macro within our migration path to ensure your diagrams are embedded and linked properly.

Below is an overview of the key migration steps from Server/Data Center to Cloud:

Detailed information on how to do this can be found here, Migrating with draw.io from Confluence Data Center/Server 8.0 to Confluence Cloud.

Migrating from one Cloud instance to another

Important: Export your PageIDs

When migrating from one Cloud instance to another Cloud instance, a key step you’ll need to take is to export your PageIDs, before migrating. This is to ensure that Confluence has correctly indexed all page attachments in the source instance, and so that your diagrams will work smoothly post-migration.

Below is a step-by-step overview on what is required at each stage:

For more detailed information and step-by-step instructions, see Migrate draw.io from one Confluence Cloud instance to another.

Jira

Migrating from on-premise to Cloud

Normally migrating between Jira instances happens automatically, the only exception is when migrating from Jira Server or Jira Data Center to Jira Cloud.

Like in Confluence, draw.io diagrams are stored as attachments, but in this case to Jira issues. In Jira Server and Data Center, draw.io diagrams are zipped into a package that contains all previous versions and revisions of the diagram.

To migrate from on-premise to Jira Cloud, your diagrams must be processed into the non-binary, single revision format used by draw.io in Jira Cloud.

Detailed information on Jira migration can be found here, Migrate draw.io from Jira Server or DC to Jira Cloud.

Embark on your migration journey with confidence

To sum up, armed with the right knowledge, migrating becomes a straightforward process. Moreover, our migration steps prioritize the security of your data: your draw.io data stays safely within your browser, stored in your Confluence or Jira instance within the Atlassian ecosystem.

With draw.io, you can embark on your deployment migration journey with confidence, knowing that your diagrams and data are in safe hands. If you need any support during your migration journey, be sure to get in touch.

Want to dive deeper into the world of draw.io? Access our linktr.ee page to follow us on social media and learn how others use draw.io, as well as pick up some helpful tips and tricks.

Out with the old, in with the new

With Server EOL around the corner, if you’re planning on migrating to Cloud or Data Center, now is the perfect time to pause and take stock of your current Atlassian setup. Is it set up the way that you want, and is it still meeting your team’s needs?

In this blogpost, we’ll be looking at the question of whether or not to migrate in the first place, followed by an overview of each stage of the migration process, to guide you on how to be fully prepared before taking the leap.

Whether you are making the big move from Server to Cloud/Data Center, or switching to draw.io from another diagramming app, remember: we’re here to help. If you need support or have questions about the migration process – before you begin, when you’re in the thick of it, or post-migration – just get in touch.

The big question

The big question to address when planning to migrate is: is it worth changing a system that is already up and running?

Sometimes the answer is clear e.g. if you’re using Confluence Server, you’ll need to migrate pretty quickly before EOL on February 15th 2024. But sometimes it’s less clear-cut, for example considering moving from one diagramming software tool to another.

Often, it feels easier to stick with what you know and avoid changing an established system. However, in the long term this can result in unnecessarily high costs. Even worse, it can result in productivity and efficiency costs too, preventing you and your teams from using alternative, better tools that serve your needs. Therefore, we would argue in many cases, it is worth changing the status quo, and evaluating your apps to ensure you’re getting the most out of them.

Your migration path might be simple or complex, but the key to a successful migration is the same: it lies in careful planning and being informed.

Let’s look at how to plan out a successful migration and the steps involved:

1. Compare

What are you migrating from, and what are you moving to? At this stage, you’ll want to weigh up the pros and cons involved in moving. For instance:

• Moving from on-premise to Cloud:
  • Advantage(s): you will benefit from all the latest updates and new feature releases in real time.
  • Disadvantage(s): as your data will move from behind the firewall to the Cloud, you may lose some control over how your data is hosted. Fortunately in the case of draw.io, your will data remains secure – all your primary data is stored in the Confluence/Jira instance of your chosen region.

For more information, see Introducing Data Governance in our Standard draw.io plan for Confluence Cloud.

• Moving from Gliffy to draw.io:
  • Advantage(s): update shape links when migrating from one Confluence deployment to another, create diagrams with AI, and more!
  • Disadvantage(s): none*

*In all seriousness, you can view a full Gliffy Comparison breakdown here.

2. Plan

The next stage is to map out your migration plan, and have this visible somewhere centrally for stakeholders, e.g. as a Jira roadmap.

You’ll want to determine:

• What steps are required to complete the process effectively?
• Who will be responsible for which phases, and how you will communicate with each other during the process?
• What are your estimated timeframes for each stage? This should be relatively flexible, allowing extra time for if any part of the process ends up taking longer than estimated.

You’ll also want to find out what support is available for your migration:

• Atlassian has the Atlassian Migration Program (AMP) which provides step-by-step guides, free migration tools, a dedicated migration support team, and a free Cloud migration trial for the length of your remaining server maintenance up to 12 months.
• draw.io offers migration support, along with clear documentation and guidance, depending on whether you’re migrating between deployments, or from a competitor to draw.io. For more information, see our Whitepaper, The Great Migration.

Atlassian also provides some handy checklists with everything you need to know before migrating. This includes recommendations like which Assistant version is best to use when upgrading, ensuring that your number of Confluence/Jira users doesn’t exceed your limit (if you do want to increase this number, you need to do this before migrating), and making sure the people responsible for migration have the right access permissions in your instance. You can view the checklists here:

1. Confluence pre-migration checklist
2. Jira Cloud Migration Assistant pre-migration checklist

3. Prepare and test

It’s a good idea at this stage to set up a sandbox environment to test how things will function post-migration. To this end, Atlassian offers a free Cloud migration trial, allowing you to explore the latest cloud-only features in a testing environment.

Once you’ve ensured the people, data, and instances are all ready to migrate, your data is backed up where possible, and any issues during testing have been fixed, it’s onto the migration phase.

4. Migrate

If you’ve completed the previous steps thoroughly and there are no blockers, then, there’s nothing stopping you – it’s time to migrate!

5. Monitor

After the migration process, it’s time to check that everything is working as expected. With draw.io, you shouldn’t have any issues… if you followed our guidance in Step 3… you did follow our guidance in Step 3 – didn’t you?

Issues unfortunately can and do crop up, sometimes straight after migrating, or over time. Monitoring systems post-migration, and letting other colleagues and teams know where to go to get support if they spot anything amiss, will help nip any problems in the bud.

A final key point is to keep good documentation throughout the migration process in order to develop any key learnings. For example, what went well during the migration, and what could be improved next time? Did any stages take more or less time than was allocated, and if so, why?

Onto the next stage

Once you have decided to take the plunge and migrate: to Data Center/Cloud, or from another diagramming app to draw.io, it’s time to get cracking!

If at any stage you get stuck or have questions about migrating draw.io, contact us at any time.

Here’s to a happy migration!

Want to dive deeper into the world of draw.io? Access our linktr.ee page to follow us on social media and learn how others use draw.io, as well as pick up some helpful tips and tricks.

The end of an era

In 2020, Atlassian made the announcement that support for Server will end on February 15th 2024. We’ll take a look at what this means for you if you are still using Server, provide detailed information on draw.io for Cloud and Data Center to help you decide which is best for you going forward, and links to further resources and support.

Life after Server

We are part of the Atlassian Dual Licensing program. This program has been extended to also include Server, provided that users purchase a subscription before February 15, 2024. This program entitles users to receive ongoing Server support until February 15 2025, provided that they purchase a draw.io for Confluence Cloud subscription. More details can be found here.

Please note: we are going to provide draw.io support for all Confluence Server versions 8.5 and above only.

So we recommend that you update to Confluence Server 8.5 and above and the corresponding draw.io version, which is 12.2.1.

draw.io is here to help on your migration journey

Migration can feel daunting, but it doesn’t have to be. We have kept the migration process, outlined below, as simple and streamlined as possible, and we are committed to helping you have a successful migration to Cloud or Data Center at every step of the way. If you do run into any problems during the process, just get in touch and we’ll be happy to help.

Migrating from Data Center/Server to Cloud

When migrating from Confluence on-premise, you can use our updated macro within our migration path to ensure your diagrams are embedded and linked properly.

Detailed information on how to do this can be found here, Migrating with draw.io from Confluence Data Center/Server 8.0 to Confluence Cloud

Migrating from one Confluence instance to another

All draw.io attachments and macros are migrated as part of the standard Confluence migration process. During the migration no data is transferred, and none of your data is stored outside of Confluence during the process.

The main step you’ll need to be aware of is that once migrated, the Confluence pageIDs will change. To ensure these IDs update appropriately, in the draw.io administration settings, you’ll simply need to:

1. Export the Page IDs from your source instance,
2. Import the Page IDs in your new target instance.

For more information, see, Migrate draw.io from one Confluence instance to another.

Migrating from Jira on-prem to Cloud

Normally, migrating between Jira instances is automatic and requires no additional steps, the only exception being migrating from Jira Server or Data Center to Jira Cloud.

Because draw.io diagrams exist as attachments in Jira issues, to migrate from on-premise Jira to Cloud, the diagrams must all be processed in the non-binary, single revision format.

To begin the migration (please note, this process is one-way and cannot be reverted):

1. Head to the draw.io Configuration settings in the administration Manage apps page,
2. Select the “Server to Cloud migration” tab,
3. Click Migrate.

For more information, see Migrate draw.io from Jira Server or DC to Jira Cloud.

If you haven’t already migrated, some helpful things to know:

Try Cloud for free

Atlassian’s transition to being a cloud-first platform means they are investing heavily into R&D for its cloud products.

To help you decide, they offer a free Cloud migration trial, where you can explore the latest cloud-only features in a sandbox environment. Within this test environment, you can of course start a free 30-day trial of draw.io for Cloud.

Here is how Atlassian is supporting users in their migration:

“To facilitate a smooth transition, we will offer three years of support and maintenance for server products and provide loyalty discounts for eligible customers to upgrade to our cloud or Data Center products at a lower price. For those ready to explore cloud, we’ve built the Atlassian Migration Program (AMP) which provides you with step-by-step guides, free migration tools, a dedicated migration support team, and a free cloud migration trial for the length of your remaining server maintenance up to 12 months.”

Cloud or Data Center?

Whether you choose to move to Cloud or Data Center, in terms of draw.io usability there are very few differences between the two: the diagram editor is essentially the same. In either version you will benefit from features like embedding diagrams in multiple pages, using the Confluence search bar to locate your diagrams, and straightfoward mass migration of Gliffy diagrams to draw.io*.

*If you’re thinking of migrating and are currently using Gliffy on Confluence Server, we suggest you first migrate to draw.io while you are still on Confluence Server (you can run the migration in trial mode, so you don’t even have to pay more). Then the move to Cloud is a breeze. For more information, see draw.io vs. Gliffy: starting a new business, all you need to know.

Our commitment to security

In Cloud or Data Center, your security is our utmost priority. Your draw.io data stays entirely in your browser; it is stored securely and exclusively in your Confluence or Jira instance, and only in Atlassian products and services.

Below is a breakdown of the key differences between using draw.io for Cloud or Data Center:

For Cloud

Cloud is the easiest way to ensure you’re always using the latest version of draw.io, and are up-to-date with the latest features and security fixes.

• Operate seamlessly: with Cloud, you avoid downtime maintenance. Atlassian takes care of security, compliance and governance, saving you time and allowing you and your teams to focus on what’s important.
• Lockdown data: you are in control. If you want to prevent all data traffic apart from that between your browser and your Atlassian instance server, you can use the lockdown function in the draw.io configuration to do so.
• Real-time updates: draw.io updates and new feature releases happen automatically in real time, meaning you are always using the most up-to-date and secure version by default.
• Collaborative editing: work with your teams synchronously, with any changes made by multiple teammates saved automatically.
• Smart Templates: use AI to automatically generate templates based on the criteria you define.

For Data Center

If you opt for Data Center, like with Server you operate in a self-managed environment. This gives full control over everything like security controls, update releases, and infrastructure choices, as this is all done behind your firewall.

With Cloud, Atlassian hosts your Cloud products for you and updates are automatic. However with Data Center, you are responsible for any maintenance and version upgrades. Either has its advantages, depending on how you wish to manage your instance.

For a full comparison, see the blogpost Differences between draw.io for Confluence Cloud and Data Center/Server.

Further resources

To find out more, check out the following articles:

draw.io:

• Differences between draw.io for Confluence Cloud and Data Center/Server
• Migration from Confluence Server – all your draw.io related options

Atlassian:

• Atlassian server is going away – now what?
• Why migrate to Atlassian Cloud?

If you need support or more information on your options, please feel free to reach out to us, and we’ll get back to you asap.

Want to dive deeper into the world of draw.io? Access our linktr.ee page to follow us on social media and learn how others use draw.io, as well as pick up some helpful tips and tricks.

The gold standard

The world of medical device compliance is a tricky one to navigate. At the top level, you have regulations from the FDA in the US, and the MDR/IVDR in Europe. Broken down, you’re then looking at sector-specific requirements like 21 CFR Part 820 in the US, and ISO 13485 + ISO 14972 internationally. Although not always a requirement, ISO 13485 certification is the gold standard, and having this certification allows companies building medical devices to operate in markets across the globe.

The good news is that there are tools out there that can help you along the way. In this blogpost, we’re diving into the world of MedTech, and how to make achieving certification like ISO 13485 and 14972 a much easier, faster, and overall better experience for teams in the industries of digital health and software as a medical device.

We’ll be looking at SoftComply, a QMS platform that seeks to automate regulatory compliance for medical device start-ups by integrating it into Atlassian Confluence and Jira.

We’ll also see how draw.io in Confluence and Jira allows you to create, edit, and customize the process flowcharts and visualizations you need, directly in your QMS space.

If you’re already using Atlassian tools like Confluence and Jira, SoftComply and draw.io are native Marketplace apps that operate seamlessly within your instance, enabling you to be more efficient and focus on the important stuff. They keep all your QMS documentation, templates, and graphic visualizations accessible and secure, as all your data stays directly in your Confluence or Jira instance.

Use SoftComply for all your QMS needs

SoftComply provides several tools for Confluence and Jira to simplify and automate compliance:

1. The SoftComply Document Manager is the only Document Management app on Atlassian Confluence Cloud with all the necessary modules. With the Document Manager app you can approve, sign, process, track and manage your electronic documents. The Document Manager has easy-to-use FDA 21 CFR 11-compliant e-signatures for document approvals.
2. The SoftComply eQMS has a Quality Manual, a Quality Policy, 25 SOPs and 77 document templates pre-filled to fast-track the development and implementation of your QMS. The SoftComply eQMS is compliant with both the FDA and the MDR regulations.

These tools cover the minimum needs of any company operating in the MedTech sector: a Quality System content and an Electronic Document Management system with electronic signatures.

Your QMS is your single source of truth

ISO 13485 itself is a process-based standard:

Source: ISO 13485:2016(en) Medical devices — Quality management systems — Requirements for regulatory purposes

And when you talk about processes, inputs, outputs and interactions, a graphical visualization is the best way to describe them.

Fortunately, you never have to leave your QMS to create the visualizations that you need: draw.io has you covered. Quickly and intuitively build and store your process flows, diagrams, and any other visualizations you can think of, directly within your single source of truth: Confluence or Jira.

The biggest advantages of creating and storing your diagrams in Confluence and/or Jira are convenience and compliance. Instead of resorting to an external app for your QMS needs, SoftComply keeps everything within your Atlassian tools. This same advantage applies to your draw.io diagrams stored within Confluence/Jira.

Having all your quality documents and diagrams stored within your QMS isn’t just a “nice-to-have” – it’s a must-have from a security, provisioning, and collaborative point of view.

Let’s take a look at some of the specific features below:

Diagramming in Confluence

Control your data and access permissions

You are in control of your data and privacy. The diagrams you create in your browser are saved in Confluence and/or Jira only – not on draw.io servers.

Customize your access levels, depending on your needs. SoftComply provides you with advanced document access control, and whichever documents you provide full, partial, or restricted access to, your draw.io embedded diagrams will follow the exact same settings.

Keep a clear path on your audit trails with revision history

draw.io assists you with your auditing and compliance requirements with its in-editor revision history. This lets you quickly see who edited what and when, and revert your diagram to a previous version if required.

Every change (or reversion) in Confluence and draw.io is captured, effectively providing a timestamp of each version of the page and the embedded diagram. It also ensures that revision history in both Confluence and draw.io are always telling the same story.

Real-time editing in Confluence

draw.io supports real-time collaboration and editing. In the same way that you can collaborate in real-time in Confluence pages, you are able to join your team members in the diagram editor and work together on a particular diagram.

A CAPA SOP. Diagram created in draw.io
Source: SoftComply eQMS

Diagramming in Jira

If you are using both Jira and Confluence, we recommend you try the draw.io app for Confluence, to take advantage of features like revision history, collaborative editing, and our whiteboard editor, which Jira doesn’t support.

If you are using Jira only, you can add and embed diagrams directly in Jira issues. This is ideal for cases where you want to store your visualized processes somewhere central. For example, you might want to store a risk management process (like the one below) in a Jira epic, for anyone working on that project to refer to, to ensure all steps in the process have been adhered to.

Cybersecurity Risk Management Process. Diagram created in draw.io
Source: AAMI TIR57: 2016 Principles for medical device security—Risk management

Export your diagrams as PDF files

By default, your diagrams exist as living files in your Confluence space. When you have finalized editing a diagram and wish to export this as an offline version, you can quickly convert your diagram to a PDF.

Export your draw.io diagram as a pdf

The best of both worlds

With the SoftComply Document Manager and eQMS, you will have all the required documents and templates to facilitate your QMS implementation, as well as the option to create your own custom forms, all within Atlassian Confluence Cloud.

For visualizations, draw.io is the perfect companion for managing diagrams in Confluence when compliance is required. No external storage and the ability to export to PDF and static versions of the diagrams are crucial to avoiding security and regulatory accidents.

In short, SoftComply and draw.io are two powerful and intuitive tools that will set you on track to achieve your compliance goals.

To find out more, you can get started with a free trial, or book a demo:

• Have you ever had to revert a change in Confluence?
• Does your company operate under standards like ISO, FEC or FDA guidelines? In other words, do you need to track changes to content and processes?
• Would you like to be able to track content changes in Confluence over time to monitor the evolution of individual decisions?

If you answered “Yes!” to one or more of the questions above, then you probably already know about the Page History in Confluence. This feature is a powerful tool for tracking the progress of your Confluence page in a timeline, and to show you at a glance who made changes in your Confluence instance at which time; even better, you can undo those changes as necessary. Today, we are looking at the topic of revision history from a different perspective, namely, from the perspective of an app embedded in Confluence. Since visualized content is often an essential part of a Confluence page (visualizing process flows or architectures as diagrams, etc.), this dynamic data should also be traceable at any time. Short side note: We are using a diagram example from our Boston Consulting Group Matrix blog post.

Click on the horizontal dots in the upper right corner to access the More actions menu and choose Page history

Native Confluence Page history

For several years now, draw.io has been integrated into the page history of every Confluence page. What does this mean in concrete terms? From the moment of creation, every draw.io diagram version is tracked in the page history (see screenshot). Every published change to the diagram, including comments, is stored as a new page version in Confluence. Of course, data such as creator/worker and time of editing can be viewed at any time. This information ensures transparency and is therefore (not only) essential for audited companies.

This is already great, but…

What do I do if I discover an error in a diagram version, which is followed by further published versions with changes to the page’s text? In this case I would lose my textual changes when jumping back to the earlier version. How can I prevent this? No problem at all! Our engineers have added a second layer, which is even more powerful than the Confluence Page History. We call it Revision history and it can be viewed in the draw.io editor.

Here you can also see the activities of everyone who published changes on the diagram or whiteboard. You have a visual reference via revision history of what specifically was changed in the visualized content. But the best part is that you can use this feature to reset individual versions of the diagram or whiteboard WITHOUT resetting entire versions of your Confluence page. With this feature you have the flexibility to adjust your written content at the same time, or independently, while the history of the edits are maintained. This is something only a Confluence embedded solution like draw.io can offer you.

There is a story about a rich businessman who would approach his bank for a sizeable loan every year.

The bank would agree; after all, business is business. But insisted on some security, the businessman would bring in his prized possession a vintage Ferrari. The bank would then hold this as security on the loan in their secure warehouse.

After the businessman sold his Ferrari, he confessed he never needed the bank loan. He explained the bank’s interest and loan fees were way less expensive than organizing the special secure parking his insurance company insisted on when he was on holiday.

The moral of the story is always to seek out cost-effective options in life.

draw.io, the powerful & elegant cost-effective option

For us, it’s not about the money, draw.io was born out of a desire to produce a powerful yet elegant diagramming application for the masses, but it had to be affordable.

Our company values

You see, it goes back to our origins, our ethos. We wanted the world to diagram, breaking down borders and enhancing communication. That’s where true creativity lives. So when we communicate and share ideas globally, we make progress; diagramming cuts through language barriers.

draw.io offers an unparalleled feature set and security for an unbeatable price

But also, it is our policy of constant research and development, bringing new features, adapting to market forces that set us apart, we lead, and our competitors follow.

Some of our milestones

• Full diagramming revision history interfaced inside of Confluence, offering compliance with the Sarbanes–Oxley Act USA.
• Recognizing the threat cybercrime presents, we adopted a rigorous approach to security. We not only meet Atlassian’s strict requirements, but we also exceed them by some margin. Giving you complete control of your security options. No other diagramming app comes close.
  Learn just how secure we are here.
• Our new Board Editor is a first for Confluence. Whiteboarding inside of Confluence will never be the same.
• Coming soon, collaborative real-time whiteboarding all inside of Confluence Cloud.
• And last but not least, it’s the application’s raw power, elegance, and ease of use. Our blogs and youtube channel highlight many use cases, workflows, and diagramming examples that our competitors struggle to replicate.

We value you, our customers

Our sense of community means we constantly strive to offer inspiration showing you precisely what draw.io can do, demonstrating new use cases and diagramming techniques. In addition, we thrive on user feedback via our Github community. So for us, it’s not about the money. It’s about great communication and visualization for professionals and students alike, or put more simply, getting the world to talk visually.

Work smarter, not harder

Compare our pricing and features with our competitors, and it soon becomes clear why draw.io is growing exponentially in popularity.
Combine this with our policy of continual development and adding new features (for free, e.g., the whiteboard), and it’s a no-brainer.

Quite simply, no one can match our ease of use, features, and perhaps most importantly, pricing.

So just like the canny businessman with his Ferrari, it’s always worth researching the market. Look closely at our competitor’s costs and see precisely what you are paying for.
Or, to put it more simply, sit down and calculate exactly how much our competitors cost compared to our pricing for a fixed number of subscriptions. You may be shocked.

Developers love us, Accountants love us, draw.io. It’s one of your better decisions.

Keen to learn more, visit our YouTube Channel for a constantly updated playlist of how-to videos.
Visit our one-stop tutorial shop to pick up all the ins and outs of draw.io diagramming.
Or book a free no-obligation demo to learn more about the limitless ways in which draw.io can make life easier and more productive for you and everyone in (and outside) your company!
Happy diagramming!

Never before has the concept of Cybersecurity been more critical than today.

A data breach can have a devastating effect on an organization’s reputation and finances.

Despite your own in-house security measures, it can be pretty sobering to think of who exactly can access your diagrams and confidential work when using external tools.

It could be an unscrupulous competitor, but increasingly, its lone actors probing for vulnerabilities and data to steal, they then actively seek markets to sell your data. So forget the image of the lone hacker sitting in a dark bedroom; cybercrime is big business.

And in terms of policing, it’s pretty much the Wild West out there. Information has value and can be sold, so it’s not surprising when our customers ask, “how safe is my information using draw.io?”

draw.io is exceptionally safe

The reason for this is how draw.io functions.

The application never sees your data. So we don’t know what you are doing with draw.io, nor do we care.
You have complete control as to who can access your data.

Data isolation

Perhaps a better analogy would be that of buying a cordless drill from a DIY store.
The store has no idea what you want to use this tool for. It could be some home improvements in your apartment, perhaps a new kitchen, or some work in your bathroom.

The DIY store has no means of knowing, nor do they care.

Not all diagramming apps are the same

Data security is our thing. None of our competitors can offer the level of security we offer. Not only do we fully comply with Atlassian’s security standards, we exceed them by quite a margin, offering levels of security no one else can even approach.

We offer options on:

• Data Residency – you decide geographically where your data resides.
• Defined Endpoints – you specify the draw.io server endpoints.
• Data transmission Lockdown – you can restrict data transmission to only occur between your browser and your Confluence Cloud instance.
• We participate in Atlassian’s Bug Bounty program.
• draw.io is verified by the Atlassian Cloud fortified program (a very select group.)

Draw.io data Governance & Data Residency

draw.io and Data Protection

draw.io & GDPR

So as well as customizable internal data security controls inside of Confluence draw.io also offers another huge advantage in the world of data security, its complaint with GDPR in Europe.

Currently, GDPR is the gold standard worldwide for data protection, and we fully comply with these regulations.

If you want to learn more about draw.io´s philosophy on security and privacy, download our whitepaper.

Keen to learn more, visit our YouTube Channel for a constantly updated playlist of how-to videos.
Visit our one-stop tutorial shop to pick up all the ins and outs of draw.io diagramming.
Or book a free demo to learn more about the limitless ways in which draw.io can make life easier and more productive for you and everyone in (and outside) your company!
Happy diagramming!

draw.io has just celebrated over 50,000 installs in Confluence. That’s almost three times as many as our nearest competitor.

So to each and every one of you – a huge thank you.

No other Marketplace app has more installs than draw.io, no other app has more reviews, and we are one of the few who hold the sought-after four-star ratings on the entire Atlassian marketplace.

Back in the day

draw.io has taken a long journey since 2001. Our founders and head engineers, Gaudenz and David, sought a solution that differed from the diagramming tools available at that time. The existing tools were either relatively crude or incredibly complex and expensive. Instead, they wanted to bring an easy way of diagramming to everybody…and they succeeded. Today, draw.io is a global product serving millions of users around the globe.

draw.io leads others follow

2016

First to offer full Diagram versioning in Confluence, full Integrated revision history.

Integrated revision history (not available in Gliffy)

First, with multipage diagrams, all dynamically linked, complex diagrams can be spread over multiple pages facilitating big picture overviews to granular, fine detail inspection.

Multipage diagrams

Introduced the Scratchpad, rapid custom shapes storage promoting faster workflows.

Scratchpad

2017

Introduced the concept of Connectors to diagramming. Connectors are a tremendously powerful addition to diagramming. Allowing shapes and their associated connecting lines to track/remain attached when editing.

Connectors

First, with Page anchors and multiple means of linking content within Confluence. The ability to insert drawings and images into Confluence and assign links to these images.

Page Anchors

Another first, Interactive diagrams, the ability to control the appearance of a diagram during presentations in real-time by using selectable layers.

Interactive diagrams

Security, draw.io introduced GDPR compliance in 2018 and operates a continual revision and improvement policy.

GDPR

2019

First, with diagram merge edits inside Confluence Server, if two or more people are working on the same diagram remotely, draw.io saves all changes, and combined with revision history, we have your back. No more accidental deletes.

Merge edits

2020

Customer Focus our continual pursuit of client satisfaction by demonstrating new and unusual Use Cases to provide our customers with fresh ideas and inspiration.
One example is our recent blog and whitepaper on “Taking diagrams into the company.”

Diagrams in HR & onboarding

Tables relaunch, our continual policy of revision and improvement. We completely revised our table tool.

draw.io tables

2021

Data Governance, your data, you decide. draw.io offers complete flexibility and control over exactly where your data is stored.

Data Governance.

Whiteboarding macro (embedded in the base product.)

The Board editor

2022 and beyond

The Board editor, its life story has only just begun.
Coming soon real-time collaborative editing.

And in the pipeline, much much more.

The timeline above is just a summary of draw.io’s achievements in just six short years. We have not only caught up with our competition but have overtaken them in both power, functionality, and number of users.

It’s our level of customization offering bespoke libraries and the ability to edit and create your own. No other application out there can match us.

Your concerns for security, privacy, and Data Governance are also ours. We understand the importance you place on data privacy by going beyond Atlassian’s requirements and what our competitors can deliver.

But ultimately, it’s our worldwide community of users who drive us on. We thrive on our feedback via Github. Perhaps you have a feature request or query, then visit our Github repository and say your piece. We love our communities feedback and actively act on suggestions and new feature requests.
draw.io Github feedback here

draw.io is genuinely is a developer’s tool. We enable you to do more, code more, helping to make the world a better place.

Keen to learn more, visit our YouTube Channel for a constantly updated playlist of how-to videos.
Visit our one-stop tutorial shop to pick up all the ins and outs of draw.io diagramming.
Or book a free demo to learn more about the limitless ways in which draw.io can make life easier and more productive for you and everyone in (and outside) your company!
Happy diagramming!