Fork me on GitHub
  • Strategy

    JGraph is firmly focused on the JavaScript client library and draw.io products based on it. The current shift to web applications is only intensifying and we spent the last 10 years positioning ourselves as the market leaders in this area.

    JGraph has over 2,000 customers in 75 countries. 74 of the Fortune 100 companies are using mxGraph technology daily within their workplace. Many of these applications are mission critical software, the companies rely on the quality of our products and the support we provide them.

  • mxGraph Open Sourced

    With our Atlassian business growing strongly, we've open sourced the core of our new business model, mxGraph. Being at the center of what we build, you can be confidence we're committed to keeping it stable, production tested and compatible with all major browsers.

  • draw.io for JIRA Cloud Launched

    The last piece of the Atlassian plugin suite is draw.io for JIRA Cloud.

  • draw.io for Confluence Cloud Launched

    Our continuing focus on the Atlassian ecosystem with our partner //SEIBERT/MEDIA produces our next product release, this time integrating with their cloud model, rather then a behind-the-firewall solution.

  • draw.io 4.0

    4.0 features include Gliffy and Lucidchart import, format sidebar panel, preview and revision history handling in Google Drive.

  • mxGraph 3.0

    The fifth generation of our architecture. We sell to many large Enterprises with long engineering cycles, so the 1.x and 2.x versions remain fully supported, we don't drop support for older versions when it suits us.

  • draw.io for Confluence goes Commerical

    With our focus on technology licensing, partnering with //SEIBERT/MEDIA, one of the leading Atlassian expert partners, was the logical step in order to bring the draw.io plugin to the level required for Enterprise users.

  • mxGraph 2.0

    mxGraph was our fourth architectural overhaul of the original 2000 diagramming component architecture. Each time the focus was on keeping the core tight, simple and ensure it just works (TM), without the developer realizing the complexity management that lies under the hood.

  • draw.io Real-Time Collaboration Launched

    Google launched a real-time collaboration service for Drive and we were one of the launch partners.

  • draw.io for Confluence Released

    Our second integration of draw.io was with Altassian's Confluence product. Launched as free plugin, within 12 months it becomes the highest user rated plugin in the entire Atlassian ecosystem (there are over 1000).

  • draw.io Integration with Google Drive

    When Google launched their Drive product we added our first storage integration. At last count there were over 200,000 Google users who had added it to their Drive.

  • draw.io Released

    At the time it was called mxGraph online. The name didn't catch, so we jumped on the .ly bandwagon and renamed to diagram.ly a month later.

    Diagram.ly experienced moderate growth, but lacked any cloud integration, users could only persist to their filesystem.

  • mxGraph 1.0 Released

    Despite many hundreds of successful commercial deployments, being engineers we waited over 3 years before we called mxGraph 1.0. Modern lean startups would not have approved of us.

    At the same time we discontinued commercial activity around the Java Swing component, the technology trend was very clear to us. Yet it was 2012 before any other company entered the commercial JavaScript diagramming library market.

  • JGraph at JavaOne

    We present JGraph at at the Moscone Centre in San Francisco for JavaOne, in the good old days of Sun.

  • First mxGraph Release

    The first release of mxGraph targetted Internet Explorer 5.5+ with the Abode SVG plugin and Firefox 1.5+. By May we replaced the need for the plugin by drawing natively in IE using VML. Abode discontinued the plugin later that year.

  • Starting mxGraph

    After a long architectural discussion the decision is taken to start a full rewrite of JGraph (named JGraphX), as well as build mxGraph. mxGraph was targetted as a fully client-side JavaScript web library that allowed easy creations of diagramming applications in a browser.

  • JGraph Layout Pro

    Our first commercial offering, JGraph Layout Pro, was launched. Layout Pro was an extension to JGraph that provided automatic node positioning in several common styles.

  • Joining Forces

    David, who had been working with JGraph in his own private UK company on business process modelling applications offers Gaudenz 300 US dollars to open source critical parts of JGraphpad, the main JGraph application at the time. Gaudenz refuses and instead they go into full partnership.

    David Benson. David is responsible for algorithms, IT and all non-engineering functions at JGraph. Previously to JGraph, David worked as an embedded software engineer for 10 years across domains such as telecommunications, defense, GPS systems and mobile phones, specializing in systems performance.

  • JGraph 2.0

    JGraph rapidly grows to become the leading open source Java Graph Visualization library. JGraph hits the 2.0 release, the first architectural change of many.

  • First Release

    JGraph 1.0 released as open source with release notes "This final release offers a 100% stable, fully standards-compliant API to display and edit graphs (networks), and has full documentation."

  • Start of JGraph

    Gaudenz starts work on JGraph for a semester project

    Gaudenz Alder. Gaudenz is responsible for all technical aspects of the products. Gaudenz started JGraph as his diploma thesis at the Swiss Institute of Technology, Zurich, in 2000. He has led all product development since and the current architectures benefit enormously from his 14 years continuous experience of designing graph visualization libraries.