Skip to content
ERPStack

Self-hostable ERP for serious operators

Control finance, operations, workforce, and security evidence in one ERP.

ERPStack gives growing organizations one self-hostable platform for the business workflows leaders actually need to trust: money, stock, people, customers, analytics, AI, audit trails, and incident evidence.

View Product Proof Explore Modules Contact Sales
Finance control
Operations execution
Workforce and security evidence
Tenant isolation
Schema-per-tenant
Access control
RBAC + approvals
Security events
SIEM producers
Operator
Grafana + Wazuh
/app/platform
Commercial proof stack
Buyer-ready product surfaces
Evidence
Finance control workspace
/app/accounting
Implemented
Operations execution workspace
/app/inventory
Implemented
Workforce governance workspace
/app/hr/employees
Implemented
BI and analytics workspace
/app/analytics
Locally verified
Security operations workspace
/app/security-operations
Locally verified
Readiness Local proof, external signoff separate

Product proof

App-derived visuals for the work buyers need to trust.

These proof surfaces are based on ERPStack workbench routes and readiness evidence. They show what the current platform demonstrates locally while keeping provider, staging, and release-owner signoff clearly separate.

Proof Area App Route Readiness
Finance control /app/accounting Implemented
Operator /app/inventory Implemented
Workforce workflow /app/hr/employees Implemented
Analytics /app/analytics Locally verified
Security /app/security-operations Locally verified

Finance control

Finance control workspace

Accounting, budgets, billing, payroll, expenses, and assets connect financial actions to audit-ready evidence.

Implemented
App-derived visual
/app/accounting
Close
Evidence tracked
Budget
Variance visible
Export
Checksummed
Area Signal Evidence
Journals Workflow controlled Audit + idempotency
Budgets Availability checked Variance proof
Payments Provider aware Settlement refs

Operator

Operations execution workspace

Inventory, procurement, sales, production, quality, documents, and POS Bridge surface daily execution status and exceptions.

Implemented
App-derived visual
/app/inventory
Stock
Traceable
Procure
Risk visible
Orders
Workflow linked
Area Signal Evidence
Inventory Movement evidence Lot/serial trail
Procurement Supplier guarded Bank-change review
Quality Override visible Inspection proof

Workforce workflow

Workforce governance workspace

HR, leave, attendance, overtime, and payroll keep sensitive workforce changes, approvals, and payments governed.

Implemented
App-derived visual
/app/hr/employees
Identity
Role scoped
Payroll
Approval gated
Export
Audited
Area Signal Evidence
Employees Sensitive changes SIEM event
Attendance Corrections routed Approval trail
Payroll Payment reviewed Reconciliation proof

Analytics

BI and analytics workspace

Governed BI uses semantic datasets, validated saved-query paths, dashboard layouts, and role-scoped variants.

Locally verified
App-derived visual
/app/analytics
SQL
Validated
Layouts
Persisted
Drilldown
Governed
Area Signal Evidence
Datasets Semantic layer RBAC scope
Dashboards Saved layouts Role variants
Reports Export aware Checksum proof

Security

Security operations workspace

Security Operations turns suspicious ERP activity into tenant-scoped incidents with Wazuh and Grafana evidence references.

Locally verified
App-derived visual
/app/security-operations
Incidents
Tenant scoped
Triage
Persistent
SLA
Tracked
Area Signal Evidence
Threats Rule grouped Wazuh proof
Operators Queue visible MTTA/MTTR
Traces Linked evidence Grafana refs

Commercial use cases

Built around the business situations buyers actually evaluate.

ERPStack is presented by operating problem, affected team, connected modules, and proof evidence so buyers can understand what the platform does without sorting through a raw feature inventory.

Compare module value
Locally verified Leadership, IT, and security operations

Self-hosted control for regulated operators

Cloud-only business tools make it hard to prove tenant boundaries, backup posture, security evidence, and operational ownership.

Self-hosting posture, tenant-aware runtime boundaries, Wazuh evidence, and Grafana references

Buyer outcomes
  • Keep ERP data on controlled infrastructure
  • Investigate tenant, user, module, log, trace, and SIEM evidence together
  • Separate local readiness from staging, provider, and release-owner signoff
Connected modules
Tenant Management Security Operations Runtime Logs Observability
Implemented Finance leaders, controllers, and auditors

Finance control and close confidence

Finance teams lose time reconciling journals, budgets, billing, payroll, expenses, assets, and external evidence across disconnected tools.

Accounting workbench, budget controls, export checksums, and payment/provider evidence

Buyer outcomes
  • Connect financial actions to audit trails and approval evidence
  • Track budgets, exports, provider references, and report snapshots
  • Give managers a clearer path from operational activity to financial truth
Connected modules
Accounting Budget Management Billing Expense Payroll
Implemented Operations, supply chain, store, and production managers

Operations execution without blind spots

Inventory, purchasing, orders, production, quality, documents, and POS activity often move faster than the back office can govern.

Inventory execution, supplier-risk paths, quality overrides, and POS Bridge policy evidence

Buyer outcomes
  • See stock, supplier, order, quality, and document exceptions in one operating model
  • Connect handoffs from store/register activity to ERP evidence
  • Preserve traceability for adjustments, exports, provider syncs, and overrides
Connected modules
Inventory Procurement Sales / CRM Production Quality POS Bridge
Implemented HR, payroll, department managers, and finance reviewers

Workforce governance for sensitive work

Employee records, attendance changes, overtime, leave, payroll payments, and exports require policy control and reviewable evidence.

Role-scoped workforce records, payroll approval evidence, and SIEM producer coverage

Buyer outcomes
  • Route sensitive changes and payroll actions through governed workflows
  • Keep attendance, leave, overtime, and payroll inputs connected
  • Make sensitive export and payment activity visible to operators
Connected modules
HR / Payroll Leave Attendance Overtime Payroll Security Operations
Locally verified Executives, service operations, BI owners, and platform admins

Executive analytics and incident evidence

Business dashboards, AI activity, incidents, and operational health become risky when they cannot be traced back to governed data.

Semantic BI layouts, AI guardrails, incident workflow, Wazuh proof, and Grafana references

Buyer outcomes
  • Use governed datasets and saved dashboard layouts for decision reviews
  • Connect incidents to Wazuh proof, trace references, logs, and operator notes
  • Keep AI/tool activity auditable and bounded by policy
Connected modules
Business Intelligence AI Security Operations Runtime Logs Automation

Buyer outcomes

Built for the decisions ERP buyers need to make with confidence.

ERPStack connects operational workflows to the evidence behind them, so leaders can see what is controlled locally, what is integration-ready, and what still needs external staging or provider signoff.

View module

Control financial truth

Accounting, budgets, billing, payroll, assets, expenses, and project costs share audit-ready evidence instead of separate spreadsheets.

Run daily operations

Inventory, procurement, sales, production, quality, documents, and POS Bridge show workflow status, handoffs, exceptions, and readiness.

Govern workforce work

HR, leave, attendance, overtime, payroll, approvals, and employee-sensitive actions keep managers close to policy and evidence.

Investigate with evidence

BI, AI, audit, SIEM producers, Wazuh, Grafana, logs, traces, and operations dashboards turn incidents into reviewable facts.

Trust, security, and self-hosted control

Commercial trust should be backed by evidence buyers can inspect.

ERPStack positions trust as a product surface: tenant isolation, RBAC, approvals, audit trails, SIEM events, Wazuh proof, Grafana references, and self-hosted operations evidence are visible commercial differentiators.

Review trust evidence
Implemented
Tenant isolation

Helps operators prove which customer workspace owned the data and action.

Schema-per-tenant business data with explicit tenant context at runtime

Implemented
RBAC and workflow control

Keeps privileged work explainable before finance, HR, inventory, or platform actions land.

Role checks, approval paths, read-only gating, and destructive-action contracts

Implemented
Audit and replay protection

Reduces duplicate external callbacks and preserves reviewable records for sensitive work.

Audit trails, idempotency, provider reference uniqueness, and export evidence

Locally verified
SIEM and incident evidence

Lets service operators see who did what, in which tenant, whether it was blocked, and why.

ERPStack security events, Wazuh proof references, incident triage, notes, and SLA lanes

Locally verified
Observability and traceability

Connects failed jobs, provider issues, security incidents, and release evidence to operations review.

Grafana dashboards, Loki log references, Tempo trace IDs, source-health and backlog signals

Staging signoff pending
Self-hosted operations posture

Supports organizations that need infrastructure ownership instead of cloud-only ERP dependency.

PostgreSQL-centered deployment design, health checks, backup/restore and rollback evidence

Commercial review path

Talk to sales with proof, boundaries, and next evidence already organized.

The contact path is designed for commercial qualification, not automatic production approval. It keeps local verification, integration readiness, staging evidence, provider credentials, and release-owner approval separate.

Contact Sales Compare Modules
Review Step What Sales Should Confirm
1. Share buyer context Identify tenant count, target modules, data residency needs, operator roles, and rollout constraints.
2. Review product proof Walk through finance, operations, workforce, BI, security, and module pages against app routes.
3. Confirm readiness boundary Separate implemented and locally verified capabilities from staging, provider, and release signoff.
4. Plan next evidence Define staging target, SIEM endpoint, provider credentials, owner approval, and acceptance checks.

Readiness

Clear status labels keep the product credible.

ERPStack public pages should show what is implemented, locally verified, integration-ready, or still waiting for staging/external signoff.

Label Meaning
Implemented Feature exists in the current app and has local verification evidence
Locally verified Verified with focused tests and/or browser smoke in local environment
Integration ready Code path exists, external provider or production endpoint signoff may be pending
Staging signoff pending Requires real staging target, database, owner approval, or external credentials

Launch copy acceptance

Public pages use consistent, honest product language.

The public site explains ERPStack as a serious ERP product while keeping local verification, integration readiness, and external signoff clearly separated.

No stale foundation-only copy

Public pages present ERPStack as a broad ERP product, not an early scaffold.

Honest readiness language

Local verification, integration readiness, and staging signoff are described separately.

Consistent module structure

Every module page uses workflows, feature groups, connected modules, governance, reports, and app-route previews.

No unsupported production claim

The copy avoids claiming production signoff where external staging and owner approval remain pending.

Commercial CTA path

Public pages expose Contact Sales and module comparison paths without depending on provider credentials.

Desktop and mobile QA

Commercial pages and module pages are browser-smoked for core copy, CTAs, discovery metadata, and overflow.