Skip to content
BOS
{{ navCtaLabel }}
Talk it through →
Managed Services

A dedicated BOS, set up and run by us.

Most teams start on the self-serve cloud plans, and should. Managed Services is for when the fit has to be exact - your own cloud or data centre, modules that do not exist yet, connectors into systems with no public API, and someone else running all of it.

Talk it through with Martin What we've already built
Custom pricing · follows volume, not headcount
01 · When you need this

Five reasons to not be on cloud.

If none of these describe you, the self-serve plans are the better buy and we will say so on the call.

{{ w.tag }}
{{ w.head }}
{{ w.body }}
02 · Bespoke modules

Already built. Already running.

These are live implementations, not a roadmap. Each one sits on the same data model as the standard modules - which is why a bespoke module threads into the rest of the business rather than bolting onto the side of it.

Live {{ b.who }}
{{ b.name }}
{{ b.body }}
Threads into: {{ b.threads }}
If what you need is not on this list, that is the normal starting position - every item here began as one customer's problem. Connectors into internal systems and industry software with no public API are part of the same work: if it has a database, it can be reached.
03 · Where it runs

Our cloud, your cloud, your building.

Cloud · self-serve
Managed · your cloud
Managed · on-premise
{{ c.k }}
{{ c.a }}
{{ c.b }}
{{ c.c }}
Full detail on encryption, backups, access and sub-processors is on the security page.
04 · Going further together

Three arrangements beyond buying software.

These are real, they are signed, and they start with a conversation rather than a form. Each one changes the relationship rather than the licence.

{{ p.n }}
{{ p.head }}
{{ p.body }}
{{ p.who }}
05 · How an engagement runs

Scoped before it is sold.

{{ h.n }}
{{ h.head }}
{{ h.body }}
Pricing follows volume, not headcount
A managed deployment is priced on the scope of what we build and run, so adding people does not repeatedly reprice the deal. That is usually the point at which larger teams find it cheaper than per-seat.
Self-serve plans
06 · The team you're trusting

Rated by the people we've already taught.

A managed build stands or falls on the people running it. These are verbatim, permissioned quotes from UseKase's Build with AI workshops - feedback about this team, before BOS existed to sell.

“{{ t.q }}”
{{ t.by }} · Build with AI participant
Shared with each participant's written permission. BOS customer stories are published at Proof once the customer signs the numbers off.
07 · The third route

Own it over time.

Most software relationships end where they start: you rent, we run it, indefinitely. There is another way to buy this. We build, we teach, we co-build alongside your team, and then we hand over the keys - leaving a platform licence rather than a per-seat bill.

We lead You lead
{{ l.n }}
{{ l.head }}
{{ l.body }}
Same team throughout. You move up the ladder at whatever pace suits you, and you can stop at any rung - plenty of businesses are happy at the point where they customise without us and never want the maintenance burden.
{{ e.tag }}
{{ e.head }}
{{ e.body }}
See the ladder alongside the plans on the pricing page →

Tell us what doesn't fit. That's the conversation.

The system you can't replace, the rule that says the data stays in the building, the module nobody sells. If self-serve is the better answer, we will tell you that instead.

Custom pricing · Your cloud or ours · Local models available
Chat with Martin