Terms of service

Subscriptions

Subscriptions are billed monthly or yearly in advance per plant, with the user band stated in your plan. Yearly terms carry the published discount. Either side may end a subscription at the end of a paid term.

What is included

Hosting, SSL, daily backups, product updates and support at your plan level. Data migration, on-site training and custom development are quoted separately.

Custom development

Custom work is delivered against a written scope. Changes to that scope are re-quoted before work starts. Ownership of custom modules is stated in your scope document.

Your data

Your data remains yours. On termination we provide a full database export and delete our copies after the retention period stated in your agreement.

Availability and support

We target 99.5% monthly availability on our managed cloud, excluding announced maintenance windows. Support response times are stated per plan.

Liability

Our liability is limited to the fees paid in the preceding twelve months. Nothing here limits liability that cannot lawfully be limited.

Asked about this

Is this a real product or a demo build?

It is a working ERP that runs a European towel manufacturing plant today. The public demo is the same build, loaded with four months of documents — sales orders, production, quality, payroll, vouchers — so you are judging the real thing, not a slide deck.

Can it be customised for a business that is not a factory?

Yes. The engine underneath — documents, stock ledger, double-entry accounting, approvals, roles, reporting — is industry agnostic. We reshape the modules, forms, documents and reports around your process. Tell us how you work and we will show you the shape it would take.

Which languages are supported?

Any language you need, including right-to-left scripts. The interface is fully translatable and we deliver the language files with your deployment. Documents and reports can print in a different language from the interface if your buyers need that.

Do we have to move all departments at once?

No. Most plants start with stores, purchase and sales, then bring production, quality and payroll in once the floor is comfortable. Approvals are switched on module by module when you are ready.

How long does implementation take?

Implementation is staged by department. The first department typically goes live in four to six weeks, with the rest following every two to three weeks. The timeline depends on how quickly you can provide masters and opening balances, and how much time your team can devote to training.

Do you support our country’s e-invoicing portal?

We build integrations for e-invoicing portals on request, provided the portal offers a REST API or file-based submission. You will need to give us the API credentials, a test environment, and a sample invoice payload. The integration is quoted separately and built after the core ERP is live.