Skip to content

Platform

Roadmap

What runs in the pilot now, what we build next, and the integrations we are exploring. Customer requests weigh in, and nothing under Next or Later runs today.

Now

What runs in the pilot today

Built and in use in the pilot. Items marked Beta run with limits, which each one names.
  • Each customer organization (a tenant) gets its own isolated environment: its own namespace, database cluster, sign-in realm and ERP instance.
  • Each workspace has its own web address under syncedoffice.com, where its users sign in.
  • Workspace users sign in to their ERP with single sign-on (OpenID Connect). (Beta)
  • The ERP back office includes accounting, in use in the pilot. (Beta)
  • Websites are published as versioned, fingerprinted builds that can be rolled back to an earlier version. (Beta)
  • SyncedOffice ships improvements every week: the changelog has at least one shipped change in each of the last 5 completed weeks.

No integration runs yet. The ones we are exploring are under Later, and you can ask for the one you need.

Roadmap

Next

What we build next

In the platform's current sequence. None of it runs today.
Roadmap

Later

Planned, and what we are exploring

Planned items not yet in the sequence, and the integrations we are exploring. Your requests decide what moves up.

For agencies

Platform and pricing

Integrations we are exploring

Grouped by what you get. Exploring means we are looking into it: none of these runs today, and names are the companies' own trademarks.

Bring your data in

Your everyday tools

Get paid and keep the books

Grow your clients' business

Automate and extend (Roadmap)

Roadmap

How will automation and AI agents (Roadmap) work? (Roadmap)

The design was accepted in September 2026. Nothing described here runs yet. Each organization's workflows run inside its own workspace, so organizations never share an agent's memory, tools or mistakes.
  • Events stay in the workspace

    A workflow in one organization's workspace cannot subscribe to another's events.

  • Actions only through tools

    Named tools with permissions; every call recorded; changes wait for a person unless a rule allows them.

  • Knowledge in the organization's database

    Search runs inside the organization's own database, not a shared index.

  • Tested before it ships

    Scenario tests that fail when behaviour breaks, and defences against instructions hidden in content.

How we decide

Customer requests weigh in. We order the work by what pilot customers ask for, what keeps each organization's data apart, and what one server can run well. Nothing here has a date until it ships, and every shipped change goes in the changelog.

Request an integration