Need help with arches?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

160 Stars 110 Forks GNU Affero General Public License v3.0 17.7K Commits 659 Opened issues


Arches is a web platform for creating, managing, & visualizing geospatial data. Arches was inspired by the needs of the Cultural Heritage community, particularly the widespread need of organizations to build & manage cultural heritage inventories

Services available


Need anything else?

Contributors list

Arches Build Status Coverage Status

Arches is a web-based, geospatial information system for cultural heritage inventory and management. Arches is purpose-built for the international cultural heritage field, and designed to record all types of immovable heritage, including archaeological sites, buildings and other historic structures, landscapes, and heritage ensembles or districts. For more information and background on the Arches project, please visit

For general inquiries and to get technical support from the wider Arches community, visit our Community Forum.

For general user installation and app documentation, visit

For the documentation pertaining to the bleeding edge code (what is in the

branch), visit We welcome new contributors; please see Contributing to Arches for details.

Issue reports are encouraged! Please read this article before reporting issues. * Report a Bug * File a Feature Ticket

Version 6.0.0 release notes

Quick Install

Installation is fully documented in the official documentation,, but assuming you have all of the dependencies installed you should make a virtual environment, activate it, and then run

pip install arches


arches-project create myproject

enter the new

cd myproject

and run

python setup_db
python runserver

and visit

in a browser (only Chrome is fully supported at this time).

If you run into problems, please review our the full installation documentation

Release Cycle

Our general release cycle will typically be a functional release (either major if there are backward incompatible changes or minor, if there are not) followed in 6-12 weeks by a bug release (patch). See for version numbering.

  • Functional releases will usually introduce new functionality to the application but could also include styling updates, enhancements to the UX, bug fixes, and general improvements.
  • Bug releases are really only concerned with fixing any bugs related to the previous release or any other issues not yet addressed
Support for previous releases

Functional releases will be supported until the next functional release. After that users are expected to upgrade to the latest release on

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.