08Operations platform
Business OS
self-hosted operations stack and automation estate
CRM, wiki, identity, invoicing, campaigns and chat on infrastructure you own rather than rent per seat.
- Status
- Live
- Period
- 2025–2026
- Relationship
- In-house venture
- Site
- Private
- Available as
- Build for you
- Retainer
The pipeline
- 01 IdentifyOne provider grants and revokes every access
- 02 OperateSelf-hosted CRM, wiki, invoicing and conversations
- 03 AutomateA shared workflow estate, namespaced per business
- 04 BrokerSecrets rotate without redeploying every consumer
- 05 OwnSubscriber list and conversation history stay yours
- 117workflows in the estate
- 9,000+subscribers on owned infrastructure
- 11businesses coordinated
- 1identity provider across all of it
The problem
Running eleven businesses on eleven stacks means eleven logins, eleven bills and no consolidated view. The alternative — a single vendor suite — means renting your operations and paying per seat for the privilege.
What we built
- 01
Self-hosted the operational stack — CRM, documentation wiki, single sign-on, invoicing, campaign email, customer conversations — on infrastructure we control.
- 02
Centralised identity behind one provider, so access is granted and revoked in one place instead of eight.
- 03
Ran the automation estate as a shared service with per-business namespacing, letting each venture inherit routing, notification and escalation patterns rather than rebuild them.
- 04
Brokered secrets centrally so credentials rotate without redeploying every consumer.
- 05
Kept the subscriber list and the conversation history on owned infrastructure — the two assets most expensive to rebuild after a vendor change.
Stack
- n8n
- PostgreSQL
- Supabase
- Authentik
- Chatwoot
- Listmonk
- Outline
- Railway
- Cloudflare
Ideal for
Groups running several businesses or brands on several stacks, tired of per-seat pricing and eleven separate logins.