CAD · head to head
KiCad vs Lonboard

KiCad
CAD
Free open source schematic capture and PCB layout with no seat, board size or layer limits
- From
- Free
- Rated
- -

Lonboard
Maps
Python map rendering in Jupyter that skips GeoJSON and moves millions of features without choking
- From
- Free
- Rated
- -
The short version
- Each has a real cost: KiCad there is no vendor obligation behind the free software, so a blocking bug is escalated to a volunteer community unless you separately buy a contract from KiCad Services Corporation.; Lonboard it is a notebook visualisation library, not a mapping application, so there is no editing, no layout, no map export for print and no sharing beyond distributing the notebook or an HTML file
- They diverge on capability: KiCad covers Schematic capture, Lonboard covers GeoArrow binary transfer.
- Prices and features above were last checked on 1 September 2026.
Where they differ
Only the attributes on which KiCad and Lonboard actually diverge.
Identical on both: starting price (Free), pricing model (Open source, no licence fee), free tier (Yes), user rating (Not yet rated).
What each one covers
Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in KiCad
- Schematic capture
- PCB layout
- No design limits
- 3D viewer
- Manufacturing output
- Scripting
Only in Lonboard
- GeoArrow binary transfer
- GeoPandas input
- deck.gl layers
- Jupyter widget
- Large dataset handling
- Styling by attribute
- Open source licence
What people use each for
The jobs each tool is most often brought in to do.
KiCad
- A hardware startup designing a multi-layer board without paying for an Altium seatnot Lonboard
- A university teaching PCB design where per-student licences are unaffordablenot Lonboard
- An open hardware project that needs design files anyone can open and modifynot Lonboard
- An engineer prototyping a board at home who needs commercial rights on the outputnot Lonboard
Lonboard
- An analyst exploring a national road or parcel dataset in a notebook where pydeck or ipyleaflet becomes unusable at that sizenot KiCad
- A researcher publishing a reproducible analysis where the visualisation must run from the same script as the processingnot KiCad
- A data scientist joining spatial data to model outputs in pandas and needing to see the result immediately without exporting to a GISnot KiCad
- A team building an internal analysis pipeline on GeoParquet that wants rendering without a serialisation step in the middlenot KiCad
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
KiCad
- There is no vendor obligation behind the free software, so a blocking bug is escalated to a volunteer community unless you separately buy a contract from KiCad Services Corporation.
- High speed design support, including advanced constraint management, differential pair and impedance tooling, remains behind Altium and Cadence, which matters as soon as boards carry fast interfaces.
- Rigid-flex and complex stack-up design is weak, so products with flex circuits usually need a commercial package.
- Component library and part sourcing integrations are thinner than the commercial tools, so parts data and availability checking is manual work someone has to own.
- Multi-engineer design data management is not provided; teams end up assembling Git workflows themselves, and merge handling on binary-adjacent design files is awkward.
Lonboard
- It is a notebook visualisation library, not a mapping application, so there is no editing, no layout, no map export for print and no sharing beyond distributing the notebook or an HTML file
- Maintenance sits with Development Seed as an open source side output of a consultancy, so roadmap priorities follow client projects and there is no support contract to buy
- Layer coverage is a subset of deck.gl, so an analyst needing a less common layer type has to drop to pydeck or write JavaScript rather than staying in Python
- It expects data already in GeoPandas or Arrow form, which means the performance benefit depends on the rest of your pipeline being Arrow-friendly; reading a large Shapefile is still the slow step
- Rendering happens in the browser, so very large datasets are ultimately limited by the client machine's memory and GPU rather than by the server, and a laptop will still fail on data a workstation handles
Pricing, plan by plan
KiCad
Free- KiCadFree
- Full suite under GPL
- No board size, layer or component limits
- Commercial use permitted
- Commercial support$undefined/year
- Support contracts sold separately by KiCad Services Corporation
- Priority issue handling and consulting
- Not included with the free software
Lonboard
Free- LonboardFree
- Open source, no licence fee
- No usage limits
- Installed from PyPI or conda
Which should you pick?
Choose KiCad if
- You need schematic capture.
- You want to start without paying.
- You work on Windows, macOS, Linux.
- You also want pcb layout.
Choose Lonboard if
- You need geoarrow binary transfer.
- You want to start without paying.
- You work on Linux, macOS, Windows.
- You also want geopandas input.
Questions people ask
- Is KiCad or Lonboard better?
- Neither clearly leads. KiCad starts at Free and Lonboard at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, KiCad or Lonboard?
- KiCad starts at Free and Lonboard at Free.
- Does KiCad or Lonboard run on more platforms?
- KiCad runs on Windows, macOS, Linux. Lonboard runs on Linux, macOS, Windows.
- Can I use KiCad for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is KiCad best used for?
- KiCad is most often used for a hardware startup designing a multi-layer board without paying for an altium seat, a university teaching pcb design where per-student licences are unaffordable, an open hardware project that needs design files anyone can open and modify, an engineer prototyping a board at home who needs commercial rights on the output. Of those, a hardware startup designing a multi-layer board without paying for an altium seat and a university teaching pcb design where per-student licences are unaffordable are not what Lonboard is typically brought in for.
- What can KiCad do that Lonboard cannot?
- KiCad covers Schematic capture, PCB layout, No design limits, 3D viewer. Lonboard covers GeoArrow binary transfer, GeoPandas input, deck.gl layers, Jupyter widget.
Answered from the vendors’ own pages
KiCad: Is KiCad really free for commercial work?
Yes. It is GPL licensed with no restriction on commercial use, board size, layer count or component count.
Lonboard: Why not just use pydeck?
pydeck serialises geometry to GeoJSON to reach the browser. Lonboard uses a binary GeoArrow pipeline, which is the reason it handles far larger datasets in the same notebook.
KiCad: Can I buy support?
Yes, but not from the project. KiCad Services Corporation sells commercial support contracts separately; CERN moved to exactly that arrangement after ending its donation programme.
Lonboard: Who maintains it?
Development Seed, a geospatial engineering consultancy, as an open source project. There is no commercial support offering.
KiCad: How is development funded?
Through donations and sponsors administered via The Linux Foundation, plus contributed engineering time.
Lonboard: Does it work outside Jupyter?
It is built as a Jupyter widget. Exporting to standalone HTML is possible, but the intended environment is a notebook.
KiCad: Is it good enough to replace Altium?
For most low and medium speed boards yes. For high speed, rigid-flex and heavily constrained designs, the commercial tools still hold a clear lead.
Lonboard: Is it free for commercial use?
Yes, it is open source with no licence fee.
Related pages
Other head to heads
- KiCad vs FreeCAD
- KiCad vs CloudCompare
- KiCad vs SolveSpace
- KiCad vs Altium 365
- KiCad vs Bambu Studio
- KiCad vs OpenSCAD
- KiCad vs PrusaSlicer
- KiCad vs Ultimaker Cura
- KiCad vs Bentley iTwin Capture Modeler
- KiCad vs RealityScan
- KiCad vs Substance 3D Designer
- KiCad vs Zoo
- KiCad vs Solid Edge
- KiCad vs Tinkercad
- KiCad vs Vectorworks
- KiCad vs deck.gl
- KiCad vs QGIS
- KiCad vs CARTO
- KiCad vs Fused
- KiCad vs Potree
- KiCad vs Foursquare Spatial Studio
- KiCad vs SAGA GIS
- KiCad vs GRASS GIS
- KiCad vs WhiteboxTools
- KiCad vs Kepler.gl
- KiCad vs Agisoft Metashape
- KiCad vs Leaflet
- KiCad vs Sygic GPS Navigation
- KiCad vs TomTom
- KiCad vs Transit
- KiCad vs Waze
- KiCad vs What3words
- KiCad vs TomTom Developer Portal
- Lonboard vs FreeCAD
- Lonboard vs CloudCompare
- Lonboard vs SolveSpace
- Lonboard vs Altium 365
- Lonboard vs Bambu Studio
- Lonboard vs OpenSCAD
- Lonboard vs PrusaSlicer
- Lonboard vs Ultimaker Cura
- Lonboard vs Bentley iTwin Capture Modeler
- Lonboard vs RealityScan
- Lonboard vs Substance 3D Designer
- Lonboard vs Zoo
- Lonboard vs Solid Edge
- Lonboard vs Tinkercad
- Lonboard vs Vectorworks
- Lonboard vs deck.gl
- Lonboard vs QGIS
- Lonboard vs CARTO
- Lonboard vs Fused
- Lonboard vs Potree
- Lonboard vs Foursquare Spatial Studio
- Lonboard vs SAGA GIS
- Lonboard vs GRASS GIS
- Lonboard vs WhiteboxTools
- Lonboard vs Kepler.gl
- Lonboard vs Agisoft Metashape
- Lonboard vs Leaflet
- Lonboard vs Sygic GPS Navigation
- Lonboard vs TomTom
- Lonboard vs Transit
- Lonboard vs Waze
- Lonboard vs What3words
- Lonboard vs TomTom Developer Portal
