Open source Gantt chart
An open source Gantt chart with nothing held back
GanttKit is MIT licensed: free for commercial use, no license key at runtime, no seat counting, and no feature reserved for a paid edition. The engine, all three renderers and every feature plugin ship under the same license, and the source is on GitHub.
MIT licensed Free commercially No license keys No telemetry No paid tier 0 core dependencies
What the MIT license gives you
| You may | Condition |
|---|
| Use it commercially, in closed-source products | Keep the copyright and license notice |
| Modify the source and ship your build | Same notice requirement |
| Redistribute, sublicense, or vendor into a monorepo | Same notice requirement |
| Use it privately, with no reporting | No warranty is provided |
That is the whole agreement. There is nothing to renew, nothing that expires in CI, and nothing that changes when your team grows.
Free as in no strings, not free as in stripped down
Commercial Gantt components are usually sold per developer seat or per application, often with a runtime license key and a support contract, and sometimes with the interesting features reserved for the top tier. Open source projects sometimes mirror that shape with an open core and a paid edition.
GanttKit does not have tiers. Concretely, all of the following are in the free package set:
- Three renderers. SVG, HTML and Canvas, driven by the same engine and the same plugins.
- Scheduling. Finish-to-start dependencies with auto-scheduling and drag-to-link.
- Hierarchy. Tree rows with expand and collapse, plus sidebar columns.
- Analysis. Baselines for planned versus actual, progress fill, date markers and bands.
- Interaction. Drag to move and resize, selection with rubber-band and context menu, tooltips, toolbar controls.
- Localization. Locale-aware timelines and translatable strings with runtime switching.
Auditable by design
Open source matters most when you can actually read the code. Two properties make that realistic here:
- Zero runtime dependencies in the core. There is no transitive tree to review, and no supply-chain surface that grows behind your back.
- Pure logic, unit tested. The engine runs in Node with no DOM, so its behavior is asserted directly rather than through screenshots.
No network calls, no analytics beacon, no license check at runtime. A chart library has no reason to talk to a server, and this one does not.
Customize without forking
The usual reason to fork a chart library is that it does not do the one thing you need. GanttKit's extension points are the same ones its own features use, so custom behavior is a plugin, not a patch.
import { GanttEngine } from '@ganttkit/core'
const engine = new GanttEngine({ rows })
engine.use({
name: 'weekend-shading',
install(ctx) {
// hooks.rows transforms data, hooks.scene adds or edits layers
return ctx.hooks.scene.tap((scene) => withWeekendBands(scene))
},
})
If you do need a fork, MIT allows it. Vendoring the packages into your own monorepo is a supported outcome, not a license violation.
Contributing
Issues and pull requests go through the GitHub repository. Bug reports that include the rows, the view mode and the expected geometry are the fastest to reproduce, because the engine can be exercised in a plain Node test without a browser.
Keep reading
Frequently asked questions
Is GanttKit really free for commercial use?
The MIT license permits commercial use, modification, distribution and private use, with no fee, no seat count and no runtime license key. You keep the copyright notice, and the software is provided without warranty.
Are any features held back for a paid tier?
No. Every renderer and every feature plugin is published under the same MIT license. There is no pro edition, no trial watermark and no feature flag tied to a license key.
Does the library phone home or collect telemetry?
No. The core has zero runtime dependencies and makes no network calls. You can verify that by reading the published bundle, which is small enough to audit.
Can I fork or vendor an open source Gantt chart library?
MIT allows forking, vendoring the source into a monorepo, and shipping modified builds. Most customization does not need a fork, because plugins can transform the row pipeline and the scene.