The OS Company
Talk to usSign in
How it works

Modules

Fifty-eight modules across nine departments. Your platform is the ones you switch on.

Every screen is a module with its own tables, sync and permissions. A client's config lists the ones they have; nothing else is built, shown or paid for.

How it works.

6 parts. Try the ones that move.

  • 1

    One catalog

    Every module, its department, what it does and what it needs, defined once and shared by every client.

  • 2

    Switched on per client

    A client's platform is a list of module ids. Switch one on and its screens, tables and sync appear on the next release.

    Try it
    Your word for a customer
    Modules
    • Order managementOperations
    • InventoryOperations
    • SubscriptionsOperations
    • Contacts and companiesCustomers
    • SegmentsCustomers
    • Email builderMarketing
    • Stripe, payments and invoicingFinance
    • Ask your dataInsights
    • AlertsInsights
  • 3

    Short names, your words

    Orders, Customers, Ask. Full names on the page; your own word for a customer everywhere.

  • 4

    Modules that need each other

    Inventory needs a commerce connection; the email builder needs Klaviyo. The catalog knows, and says so before anything is built.

  • 5

    On the build list

    A module that is not built yet still shows in the sidebar, marked, with a box to tell us what you need there.

  • 6

    Bespoke, kept apart

    Anything unique to your business lives in your own overrides folder. The shared product improves for everyone; yours stays yours.

What changes.

  • Start with a few modules. Add more as you grow.
  • The sidebar shows only what you use, under short plain names.
  • Modules still on the build list are visible and marked, so you can ask for them.
  • Bespoke work lives in your own overrides, never in the shared product.

Only what you use. All of it yours.

Talk to us about building yours, or sign in if you already have one.

Talk to usSign in

The other layers.