Multi-tenant by architecture
Every record is tenant-scoped and enforced at the database with row-level security. Platform and tenant access planes are kept separate by design, not by convention.
Run your operations on one accountable platform.
Aster is a multi-tenant ERP for operational businesses — health operations today, with accounting, inventory, and procurement on the same identity, entitlement, and audit backbone.
Entitlement-controlled modules
Platform administration grants modules per tenant. What staff can open is the intersection of tenant entitlements and their own permissions — nothing more.
Audited support access
Cross-tenant support runs through explicit, time-bound impersonation with a full audit trail. There is no silent administrative path into tenant data.
Modules
One platform. Modular operations.
Modules are granted per tenant and share the same tenancy, identity, and accounting backbone — a modular monolith, not a patchwork of disconnected products.
Health Operations
Flagship module
Outpatient encounters, pharmacy dispensing, and operational billing for clinics and health institutions — built for daily front-desk and clinical throughput.
Accounting
Baseline — included with every tenant
Ledgers, postings, and reversals form the financial backbone every other module posts into. Corrections are reversals, never silent edits.
Inventory
Operational
Append-only stock ledger with branch-scoped balances and cost-of-goods integration into accounting.
Procurement
Operational
Supplier workflows and purchasing that settle into accounting through explicit integration contracts.
Fleet & Spatial Operations
In development
Live fleet telemetry, operational corridors, and route-deviation alerting — the emerging spatial edge of the platform.
Trust
Security and access, by default.
The guarantees below are properties of the platform, not optional configuration.
Tenant-bound sessions
A session belongs to one workspace for its entire lifetime. Changing tenant context requires signing in again — there is no ambient cross-tenant state.
Branch-aware entry
Branch resolution happens before module routing, so every operational action carries an unambiguous branch scope from the first click.
Deterministic module entry
Login routes each person to exactly the modules they can use. One module opens directly; multiple modules present a clear access hub; no access is stated plainly.
Append-only financial history
Stock movements and ledger postings are append-only. Sensitive actions stay auditable, and corrections leave a trail instead of overwriting it.
Sign in with your workspace code.
Your workspace decides what you see — modules, branches, and permissions resolve the moment you sign in.