About · Operating model

One bench. Three products.
One thesis.

How Lodat is structured, why we run three products from one engineering team, and how the pieces fit together.

Operator company, not a holdco.

Lodat is one legal entity, one engineering team, one product organisation. VenueOS, Keptable and CoreShift are not separate companies. They’re three branded products shipped from the same bench. Same model as Atlassian (Jira / Confluence / Trello) or 37signals (Basecamp / Hey). One operating muscle, multiple buyer surfaces.

Why three.

Each product earns its place by addressing a buyer beachhead the others can’t. VenueOS goes deep on hospitality, where Lodat has operator credibility. Keptable goes wide on the held-appointment problem, which exists in eight sectors. CoreShift goes wide on personal change, where the same engineering posture meets a different kind of life. Three products, three motions, one engineering posture.

Shared backbone.

All three products run on the same architectural defaults. Multi-tenant Postgres with row-level security. Stripe-native payments. Audit-first design. Every decision the platform makes leaves a trail. Clinical-grade data handling on consent and access, even where the product is wellness, not regulated care. The choices we made for one product compound across the others.

Operator credibility, then horizontals.

VenueOS is the credibility play: a real venue runs on it, every release ships there first, every claim we make can be checked against a real shift. That credibility unlocks the horizontals. Keptable and CoreShift. Which would be harder to ship cold. The vertical earns the trust; the horizontals scale the work.

Honest about what each is.

VenueOS is live. Keptable is in pre-launch with a pilot programme. CoreShift is in build-up to launch. We label products by where they actually are. We don’t coming-soon a product we haven’t started, and we don’t pretend pre-launch is launch. Pricing follows the same rule.

Sequencing, deliberately.

We ship one product at a time to public availability. VenueOS first. Keptable second, on top of the pattern VenueOS proved. CoreShift third, when its readiness clears the bar. Sequencing matters. Three half-shipped products serve nobody.

Read the story.

How Lodat got here, and the venue it was built inside.