Centurion ERP
"`An ERP with a large emphasis on the IT Service Management (ITSM) and Automation."
Whilst there are many Enterprise Rescource Planning (ERP) applications, most suffer one or more of the following issues:
- High upfront and hidden costs
- Critical features locked behind paywalls
- Complex, bloated deployments that overwhelm smaller teams
- Poor usability and steep learning curves that frustrate staff
- Painful integrations and migration headaches
- Ongoing maintenance costs and technical debt
Centurion ERP is developed as a community project, a true open source product with no restrictions or hidden tiers. It is not an “open core” model with premium features locked away, nor a downstream edition of a paid product. Everything Centurion ERP offers is freely available to everyone. Centurion ERP allows users to adopt functionality at their own pace, avoiding unnecessary complexity. Centurion ERP is designed to include all the software features a user needs within a single platform, enabling true consolidation and reducing reliance on multiple external systems; where a specific feature is missing, the system can be easily extended to fill the gap.
By addressing these common challenges directly, Centurion ERP aims to provide a practical, sustainable ERP that supports growth without introducing unnecessary barriers.
From the creator:
An ERP, depending on industry; can have a lot of modules. This equates to a lot of time to design and implement--Reality is, I'm a single person and as such will not be able to add a lot of features due to that fact. This is not an intent that Centurion ERP will not have those modules/features added/created. In this circumstance it will be left up to the community to implement. With that said, my focus is to provide a system that is not only an IT Infrastructure Library (ITIL), but that of which will connect to other ITSM systems, i.e. AWX for automation orchestration. In addition, also provide the base modules to Centurion ERP so that it can be easily extended with the required features that one would find within an ERP.
Documentation
Documentation is broken down into three areas, they are:
Specific features for a module can be found on the module's documentation un the features heading
Development
It's important to us that Centurion ERP remaining stable. To assist with this we do test Centurion during it's development cycle. Testing reports are available and can be viewed from Github.
Info
If you find any test that is less than sufficient, or does not exist; please let us know. If you know a better way of doing the test, even better. We welcome your contribution/feedback.
Features
Feature table uses the following keys:
- :white_check_mark: Feature available.
- :recycle: Under development. Some features may be available.
- :x: Planned feature, development has not started.
| Area | Feature | Status | Notes |
|---|---|---|---|
| Accounting | see #88 | ||
| Accounts Payable | :x: | ||
| Accounts Receivable | :x: | ||
| Asset Management | :recycle: | see #89 | |
| Budgeting & Forecasting | :x: | ||
| Cash Management | :x: | ||
| Cost Center Management | :x: | ||
| Expense Management | :x: | ||
| Financial Reporting & Analytics | :x: | ||
| General Ledger | :x: | see #116 | |
| Income Management | :x: | ||
| Investment Management | :x: | ||
| Tax Management | :x: | ||
| Core | |||
| API | :white_check_mark: | ||
| Application wide settings | :white_check_mark: | ||
| Audit History | :white_check_mark: | ||
| Corporate Directory (contacts) | :white_check_mark: | see #705 | |
| Location Management (Regions, Sites and Locations) | :x: | see #62 | |
| Markdown | :white_check_mark: | ||
| Multi-Tenant | :white_check_mark: | ||
| Roles (RBAC) | :white_check_mark: | ||
| Single Sign-On {SSO} | :white_check_mark: | ||
| Soft Deleting | :x: | ||
| Customer Relationship Management (CRM) | :x: | see #91 | |
| Customers | :x: | ||
| Field Service Management | :x: | ||
| Invoice Management | :x: | ||
| Pricing & Discounts | :x: | ||
| Quote & Proposal Management | :x: | ||
| Returns & Claims Management | :x: | ||
| Sales Order Management | :x: | ||
| Development Operations (DevOps) | see #68 | ||
| Feature Flag Management | :white_check_mark: | ||
| Test Management | :x: | ||
| Release Management | :x: | ||
| Repository Management | :recycle: | see #115 | |
| Requirements Management | :x: | ||
| Version Control / Source Code Management | :x: | ||
| Public Repository Management | :x: | see #998 | |
| Facilities Management | see #574 | ||
| Building Management | :x: | ||
| Maintenence Management | :x: | ||
| Room Management | :x: | ||
| Fleet Management | |||
| Vehicle Management | :x: | ||
| Human Resource Management | :recycle: | see #92 | |
| Employee Records | :x: | ||
| Maintenence Management | :x: | ||
| Onboarding / Offboarding | :x: | ||
| Self-Service | :x: | ||
| Idea & Innovation Management | :x: | ||
| Idea Capture / Submission | :x: | ||
| IT Infrastructure Management (ITIM) Data Center Infrastructure Management (DCIM) |
|||
| Bare Metal Provisioning | :x: | ||
| BMC Server Management | :x: | ||
| Cable Management | :x: | ||
| Capacity Planning | :x: | ||
| Cluster Management | :recycle: | ||
| Rack Management | :x: | ||
| Service Management | :white_check_mark: | ||
| User Provisioning / De-provisioning | :x: | ||
| Virtual Machine Management | :x: | see #73 | |
| IT Service Management (ITSM / ITIL) | |||
| Certificate Management | :x: | ||
| Change Management | :recycle: | see #90 | |
| Configuration Management | :white_check_mark: | ||
| Database Management | :x: | see #72 | |
| Incident Management | :recycle: | see #93 | |
| IT Asset Management (ITAM) | :white_check_mark: | ||
| Knowledge Base | :white_check_mark: | ||
| Licence Management | :x: | see #4 | |
| OS Asset Management (OAM) | :white_check_mark: | ||
| Problem Management | :recycle: | see #95 | |
| Release and Deployment Management | :x: | see #462 | |
| Service Catalog | :x: | see #384 | |
| Service Level Management | :x: | see #396 | |
| Service Request Management | :recycle: | see #96 | |
| Software Asset Management (SAM) | :white_check_mark: | ||
| Software Package Management | :x: | see #96 | |
| User Access & Roles | :x: | see #70 | |
| Vulnerability Management | :x: | see #3 | |
| Workflow Automation | :x: | Possibly going to be done as integration with EDA Server and AWX | |
| Project Management | |||
| Milestones | :white_check_mark: | ||
| Projects | :white_check_mark: | ||
| Roadmap | :x: | ||
| Tasks | :recycle: | ||
| Supply Chain Management (SCM) | |||
| Contract Management | :x: | ||
| Purchase Requisition & Order | :x: | see #94 | |
| Supplier Management | :x: | see #123 | |
| Inventory Management | :x: | ||
| Purchase Invoice Management | :x: | ||
| Third party Integrations | |||
| ArgoCD | :x: | ArgoCD is a Continuous Deployment system for ensuring objects deployed to kubernetes remain in the desired state. see #77 | |
| AWX | :x: | AWX is an Automation Orchestration system that uses Ansible for its configuration. see #113 | |
| Companion Ansible Collection | :recycle: | ||
| Gitea | :x: | ||
| Github | :recycle: | ||
| Gitlab | :recycle: | ||
| Kubernetes | :x: | see #999 |
To find out what we are working on now please view the Milestones on Github.
Licencing
Centurion ERP is released under the GNU Affero General Public License (AGPL-3.0-only).
The AGPL guarantees full access to the source code, with the freedom to use, modify, and extend the system as needed. Unlike other licenses, the AGPL ensures that improvements made are shared back with the community. This protects users from vendor lock-in and ensures that Centurion ERP remains transparent, auditable, and community-driven over the long term.
A common concern with this and similar licences, is the idea of “having to share code.” This often causes confusion and leads decision makers to opt away from using software with these conditions. This confusion generally stems from a lack of understanding of what the "sharing code" means. Simply put, any modification that is made to Centurion, not your data (which is anything you enter into Centurion ERP once it's installed); is what is shared with the community. This condition in particular enforces that any improvements anyone makes then become available for everyone, strengthening Centurion ERP as a product.
Finally, if Centurion’s licence were ever changed to something more restrictive, the community can always fork the last AGPL release. This safeguard ensures that Centurion ERP — or its successor forks — will always remain free and open.
Example
Company ACME has decided to use Centurion ERP. They are a manufacturing company. Centurion is missing the manufacturing features. So company ACME requires a software developer (or someone skilled enough) to extend Centurion ERP with the features required. ACME then deploys Centurion ERP with the features they added to Centurion ERP. In addition, ALL of the work the software developer does "must" be publically available (AGPL requirement).
Now company Homewares comes along whom is also a manufacturer. They see that Centurion ERP has the manufacturing features, thanks to ACME company. However in this case, Homewares company wants to add additional features. to do this they fork ACME companies work and add the new features. Again they share all of the work they did.
Now there are two different manufacturing "feature sets". ACME can if they choose, use Homewares manufacturing "features" or they can stick to their own, which also incldues ONLY extending their own manufacturing "features".
About:
This page forms part of our Project Centurion ERP.
Page Metadata
Version: ToDo: place files short git commit hereDate Created: 2024-06-17
Date Edited: 2025-09-28
Contribution:
Would You like to contribute to our Centurion ERP project? You can assist in the following ways:
- Edit This Page If there is a mistake or a way you can improve it.
- Add a Page to the Manual if you would like to add an item to our manual
- Raise an Issue if there is something about this page you would like to improve, and git is unfamiliar to you.
ToDo: Add the page list of contributors