Skip to content

Platform

A back office for every organization

Each customer organization gets its own ERP instance with its own database. Accounting runs in the pilot; more modules are on the roadmap.

Today

What does each organization's back office include?

  • Its own ERP instance

    Every customer organization's workspace runs its own ERP instance. No ERP is shared between organizations.

  • Its own database

    Every customer organization's workspace has its own database cluster. No database is shared between organizations.

  • Accounting first

    The ERP back office includes accounting, in use in the pilot. (Beta)

How it is created

How is a back office set up?

An operator builds each organization's environment from one definition, so every workspace is put together the same way.

One definition in, one workspace out

Same order, every time

  1. 01Namespace
  2. 02Network policy
  3. 03Resource quota
  4. 04Database
  5. 05ERP instance
  6. 06Sign-in realm
Each workspace is created automatically from one definition, running the same steps in the same order every time. Among its steps, in this order: namespace, network policy, resource quota, database, ERP instance and sign-in realm.

Sign-in

How do a client's staff sign in?

Each workspace has its own web address under syncedoffice.com, where its users sign in. Every customer organization's workspace has its own sign-in realm, so its users and roles are kept apart from every other organization's.

Staff sign in to the ERP with single sign-on. Roles (admin, member, viewer) come from the sign-in realm and refresh at every sign-in. (Beta)

Next

What is coming to the back office?

More modules, and ways to bring your records in: importing from spreadsheets or Odoo is on the list of integrations we are exploring.
Roadmap: not available yet
  • Orders, inventory, purchasing and invoicing, verified for pilot workspaces. (Roadmap)
The full roadmap

FAQ

Questions and answers

Does each customer get its own ERP?

Yes. Each customer organization's workspace runs its own ERP instance, with its own database, shared with no other organization.

Which parts of the ERP can a pilot client use?

Sign-in, the dashboard and accounting have been checked in the pilot. (Beta) Other ERP modules have not been checked for a workspace yet, so we do not list them as available.

Why not one ERP shared by every customer?

A shared ERP keeps every customer's records in the same tables and relies on software filters to keep them apart. A separate instance with its own database has nothing shared to filter.

Can I import my existing data?

During the pilot we plan each move with you, starting from the spreadsheets or exports you have today. There is no self-service import tool yet: CSV and spreadsheet import is an integration we are exploring.

See a workspace with your own data in mind.

Tell us what you run today. How each organization is kept apart

Join the pilot