Libraries · head to head
ArchivesSpace vs Lonboard

ArchivesSpace
Libraries
Open source archives information management application
- 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: ArchivesSpace requires Java 17 or 21 (or Java 11/17 for older versions), adding infrastructure complexity; 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: ArchivesSpace covers Accession management, Lonboard covers GeoArrow binary transfer.
- Prices and features above were last checked on 1 September 2026.
Where they differ
Only the attributes on which ArchivesSpace and Lonboard actually diverge.
| Attribute | ArchivesSpace | Lonboard |
|---|---|---|
| Pricing model | subscription | Open source, no licence fee |
| Platforms | Ubuntu Linux, macOS, Windows | Linux, macOS, Windows |
| Category | Libraries | Maps |
| Founded | 2013 | Unknown |
Identical on both: starting price (Free), 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 ArchivesSpace
- Accession management
- Resource description
- Digital object management
- Agent and subject authorities
- Location management
- Assessment module
- Public user interface
- EAD/MARCXML export
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.
ArchivesSpace
- Digital archive managementnot Lonboard
- Repository managementnot Lonboard
- Cultural heritage preservationnot Lonboard
Lonboard
- An analyst exploring a national road or parcel dataset in a notebook where pydeck or ipyleaflet becomes unusable at that sizenot ArchivesSpace
- A researcher publishing a reproducible analysis where the visualisation must run from the same script as the processingnot ArchivesSpace
- A data scientist joining spatial data to model outputs in pandas and needing to see the result immediately without exporting to a GISnot ArchivesSpace
- A team building an internal analysis pipeline on GeoParquet that wants rendering without a serialisation step in the middlenot ArchivesSpace
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
ArchivesSpace
- Requires Java 17 or 21 (or Java 11/17 for older versions), adding infrastructure complexity
- Mandatory Solr 9 (or 8 for older versions) for all production deployments since v3.2.0
- Production deployments must use external MySQL 5.x or 8.x; embedded database only for testing
- Minimum 1 GB RAM required, 2 GB recommended; Docker installation recommended as of v4.0.0 due to complexity
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
ArchivesSpace
Free- Very Small$300/year
- Academic/Public Library tier (JSTOR/Artstor Very Small, etc.)
- Non-Academic: 0-50 FTE staff
- Small$1000/year
- Academic/Public Library tier (JSTOR/Artstor Small, etc.)
- Non-Academic: 51-150 FTE staff
- Medium$3000/year
- Academic/Public Library tier (JSTOR/Artstor Medium, etc.)
- Non-Academic: 151-300 FTE staff
- Large$5000/year
- Academic/Public Library tier (JSTOR/Artstor Large, etc.)
- Non-Academic: 301-400 FTE staff
Lonboard
Free- LonboardFree
- Open source, no licence fee
- No usage limits
- Installed from PyPI or conda
Which should you pick?
Choose ArchivesSpace if
- You need accession management.
- You want to start without paying.
- You work on Ubuntu Linux, macOS, Windows.
- You also want resource description.
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 ArchivesSpace or Lonboard better?
- Neither clearly leads. ArchivesSpace 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, ArchivesSpace or Lonboard?
- ArchivesSpace starts at Free and Lonboard at Free.
- Does ArchivesSpace or Lonboard run on more platforms?
- ArchivesSpace runs on Ubuntu Linux, macOS, Windows. Lonboard runs on Linux, macOS, Windows.
- Can I use ArchivesSpace for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is ArchivesSpace best used for?
- ArchivesSpace is most often used for digital archive management, repository management, cultural heritage preservation. Of those, digital archive management and repository management are not what Lonboard is typically brought in for.
- What can ArchivesSpace do that Lonboard cannot?
- ArchivesSpace covers Accession management, Resource description, Digital object management, Agent and subject authorities. Lonboard covers GeoArrow binary transfer, GeoPandas input, deck.gl layers, Jupyter widget.
Answered from the vendors’ own pages
ArchivesSpace: Is ArchivesSpace free to use?
ArchivesSpace application is free to download and use. However, community membership is required and costs $300-$7,500 annually depending on organization type and size.
SourceLonboard: 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.
ArchivesSpace: How much does ArchivesSpace membership cost?
Membership costs range from $300/year (Very Small institutions) to $7,500/year (Very Large institutions). Costs are based on FTE staff size for non-academic archives (0-50 staff: $300; 400+ staff: $7,500) or JSTOR/Artstor classification for academic institutions.
SourceLonboard: Who maintains it?
Development Seed, a geospatial engineering consultancy, as an open source project. There is no commercial support offering.
ArchivesSpace: When does the ArchivesSpace membership year run?
ArchivesSpace membership runs from July 1 to June 30 each year and renews annually. New members joining outside this period receive prorated fees for their initial term.
SourceLonboard: 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.
Lonboard: Is it free for commercial use?
Yes, it is open source with no licence fee.
Related pages
More on ArchivesSpace
Other head to heads
- ArchivesSpace vs Archivematica
- ArchivesSpace vs DSpace
- ArchivesSpace vs CollectiveAccess
- ArchivesSpace vs CONTENTdm
- ArchivesSpace vs Omeka
- ArchivesSpace vs Ex Libris Alma
- ArchivesSpace vs VuFind
- ArchivesSpace vs Evergreen ILS
- ArchivesSpace vs Koha
- ArchivesSpace vs FOLIO
- ArchivesSpace vs SirsiDynix Symphony
- ArchivesSpace vs Axiell Collections
- ArchivesSpace vs Base UI
- ArchivesSpace vs daisyUI
- ArchivesSpace vs Leafmap
- ArchivesSpace vs OCLC WorldShare Management Services
- ArchivesSpace vs deck.gl
- ArchivesSpace vs QGIS
- ArchivesSpace vs CARTO
- ArchivesSpace vs Fused
- ArchivesSpace vs Potree
- ArchivesSpace vs Foursquare Spatial Studio
- ArchivesSpace vs SAGA GIS
- ArchivesSpace vs GRASS GIS
- ArchivesSpace vs WhiteboxTools
- ArchivesSpace vs Kepler.gl
- ArchivesSpace vs Agisoft Metashape
- ArchivesSpace vs Leaflet
- ArchivesSpace vs Sygic GPS Navigation
- ArchivesSpace vs TomTom
- ArchivesSpace vs Transit
- ArchivesSpace vs Waze
- ArchivesSpace vs What3words
- ArchivesSpace vs TomTom Developer Portal
- Lonboard vs Archivematica
- Lonboard vs DSpace
- Lonboard vs CollectiveAccess
- Lonboard vs CONTENTdm
- Lonboard vs Omeka
- Lonboard vs Ex Libris Alma
- Lonboard vs VuFind
- Lonboard vs Evergreen ILS
- Lonboard vs Koha
- Lonboard vs FOLIO
- Lonboard vs SirsiDynix Symphony
- Lonboard vs Axiell Collections
- Lonboard vs Base UI
- Lonboard vs daisyUI
- Lonboard vs Leafmap
- Lonboard vs OCLC WorldShare Management Services
- 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
