Frequently asked questions

A multi-tenant mini ERP for small and mid-sized organizations. Four modules ship today — Finance, Human Resources, CMS and Business Partner — behind one sign-in, one permission model and one audit trail.

Finance (invoices, estimates, expenses, payments, journals and reports), Human Resources (employees, attendance, leave, payroll, shifts and overtime), CMS (documents, media, announcements, knowledge base, banners and FAQ) and Business Partner (partners, customers, suppliers, contacts and agreements).

Yes. Business Partner is the single party master. A Finance invoice is issued to a Business Partner record tagged as a customer — there is no separate "finance customer" list to keep in sync.

The platform is built so a new module (Inventory, Procurement, CRM, Sales, Manufacturing, Asset Management, Helpdesk) is added without changing the architecture. Each one reuses the same tenancy, RBAC, audit and UI foundations.

Yes. Your identity is global — one email, one password, one login — and you belong to as many organizations as you are invited to. A workspace switcher in the header moves you between them without signing out, and your roles are resolved per workspace.

That is the expected state. Registration creates an identity, never an organization: access is granted by an administrator, never by signing up. Ask an admin to add your exact email address and you will land in the workspace automatically.

No form ever asks for one. Signing in establishes who you are; your membership decides where you land — your default workspace, or your oldest one if you have not flagged a default.

Google sign-in is supported and matches on email, so it never creates a duplicate account. Multi-factor authentication is available in the login app, and one sign-in covers every module app on the domain.

Every business table carries a tenant id, and the tenant filter is applied in the shared repository layer rather than in individual handlers — so a query that forgets it cannot be written. The active workspace comes from your signed session, never from a header or URL a caller can set.

Two axes. Type-level asks whether your role may perform an action on a resource; record-level asks which rows — "own" limits you to records you created, "all" gives tenant-wide reach. Both are enforced server-side, so a guessed record id returns "not found" rather than someone else's data.

Every create, update and delete records the user, tenant, IP, device, before and after values, timestamp, action and route, on a stream separate from application logs and queryable per organization. Business records are soft-deleted, so nothing disappears silently.

It is soft-deleted: hidden from lists and lookups, retained in the database with who deleted it and when, and captured in the audit trail.

Pricing is quoted per organization at this stage rather than published as a monthly rate — the plan depends on which modules you turn on, how many people use them and whether you self-host. Tell us your shape and you get a straight number.

Get in touch. We walk through your modules and user count, set up a workspace, and seed the roles your team actually needs before anyone signs in.

Yes. It runs on Node.js 20 with MariaDB and Redis, ships with Docker files and a PM2 production setup, and all configuration comes from environment variables — nothing is hardcoded to a hosted environment.

Timezone, language, date format, number format and currency are set per organization. Amounts are stored as exact integers and rendered with the currency's own precision, so no rounding creeps in between the ledger and the screen.