vosetu.

SaaS & Mandantenfähige Architektur

Vosetu is a SaaS factory: we built 46 sector products on the same core. Tenant isolation, subscriptions, role management and scaling are not something to rediscover for us — they are our daily work.

Mit einem Experten sprechen

One core, unlimited tenants

Building SaaS isn't making an existing app 'multi-user'; it's a different architectural decision from day one. Tenant isolation, subscription and plan management, usage limits and gating decisions aren't features patched on later — they're foundations that belong in the core from the start. We haven't built this once; we've built it 46 times.

From health to hospitality, sports to field services, we've built 46 sector SaaS products on the same multi-tenant core. Five of them are genuinely live today, used by real businesses: Vosetu CMS, Horeca, Vosetu Flight, Belora and Emlora. Your SaaS is built on that field-tested core too — not invented from scratch.

  • 46 sector SaaS products, one core
  • Live in 5 products: CMS, HoReCa, Flight, Belora, Emlora
  • Tenant isolation in the architecture from day one
  • Subscription + gating engine as standard

5 capabilities a SaaS needs from day one

Multi-tenant architecture design
Tenant isolation and data security
A subscription, plan and usage-limit engine
Role/permission and organization management
Infrastructure ready for scalable, multi-region deployment

5 services living under the SaaS core

Each can be set up independently, yet all share the same tenant, user and permission model.

Multi-tenant architecture setup

Schema/row-level tenant isolation, per-tenant settings and branding; one tenant's data never leaks into another's.

Subscription & gating engine

Plan, trial period and usage limits come together in one engine; the decision of who has a feature turned on lives in a single service.

Role/permission & organization management

Multi-user, role-based authorization within a tenant; each customer sets up their own organization.

Fast adaptation to a sector vertical

The shared SaaS core turns quickly into a new vertical with sector-specific modules — bookings, stock, subscriptions.

Scaling & multi-region deployment

With containerization, caching and monitoring, only the infrastructure grows as tenant count rises — not the pain.

How AI fits into a SaaS product

01

The data is already in one core

Every tenant's bookings, orders and reporting data already sit in one, typed data model — a natural starting point for adding AI-assisted search, recommendations or summarization. We don't claim a pre-built 'AI module'; what we build is the clean data foundation those features stand on.

  • A typed, single-source data model
  • Tenant-level data isolation is preserved
  • AI is added as an adapter, not into the core
02

The gating engine manages AI features too

The decision of which plan can use an AI feature (e.g. smart recommendations, auto-summarization) lives in the same single gating service as every other feature. That means adding AI to a higher plan is changing a line in a constant, not embedding a new 'if' block into a screen.

  • Plan-based AI feature toggling
  • No 'if' blocks buried in screens
  • Only the adapter changes when the source changes

The 3 layers of building SaaS at scale

01

Multi-tenant architecture

Tenant isolation, a typed data model and the identity/permission foundation are set up first; every new tenant rests on this base without touching the core.

02

Integrations

Payment providers, e-invoicing, SMS and email are added as independent adapters; when a provider changes, only that adapter is updated.

03

DevOps

With containerization, CI/CD and monitoring, deployment scales automatically as tenant count grows; downtime risk doesn't depend on manual steps.

8 sectors our 46 SaaS products span

Each cluster has its own way of working, yet all share the same tenant, subscription and permission core.

Health & care

Clinics, dental, physiotherapy, pharmacy, lab — 13 sector SaaS products.

Hospitality & travel

Hotels, guesthouses, dorms, HoReCa, tour operators, flight schools — Vosetu Flight is live here.

Sports & lifestyle

Gyms, turf fields, clubs, daycares, study centers — sharing the same membership/booking core.

Services & field

Laundries, repair shops, auto services, moving, cargo, tailors — 11 field-focused SaaS products.

Commerce & office

Real estate agencies (Emlora), jewelers, law, accounting, property management, farms, fulfilment.

Publishing & corporate

Vosetu CMS: a multi-tenant content platform managing unlimited sites on one infrastructure.

HoReCa & food service

Horeca: menu, tabs, kitchen display and till in one panel — a live product.

Beauty & appointments

Belora: appointments, staff and register management for hair and beauty salons — a live product.

The technology we build on

Core
  • .NET 9
  • ASP.NET Web API
  • PostgreSQL
Tenancy
  • Schema/row-level isolation
  • Plan + limit + gating engine
Interface
  • Next.js
  • Angular
  • TypeScript
Scale
  • Redis
  • Docker
  • MinIO

Who works on your SaaS project

Architect — sets up tenant isolation, the typed data model and the gating engine
Backend developer — writes the layered (service/bll/dal) API on .NET 9
Interface developer — builds the Next.js (public) and Angular (panel) sides in parallel
DevOps engineer — sets up containerization, CI/CD and monitoring
Product/project manager — runs plan, scope and roadmap together with you
46
Sector SaaS products
5
SaaS products live
22
Industry verticals
.NET 9
Modern core stack

Frequently asked

Do you have a genuinely live SaaS product, or is it all prototypes?

5 of our 46 products are genuinely live today and used by real businesses: Vosetu CMS, Horeca, Vosetu Flight, Belora and Emlora. The rest are ready sector solution definitions on the same core — they're published as demand arises.

How is tenant isolation ensured?

The data model is separated by tenant from the start; schema- or row-level isolation is chosen based on the project's scale. A user from one tenant can never access another tenant's data under any condition — this isn't a control added later, it's the architecture itself.

Do you build the subscription and payment infrastructure?

Yes. We build a subscription engine covering plans, trial periods, usage limits and payment-provider integration; we've built this engine many times across 46 SaaS products.

Do we need to bring a from-scratch SaaS idea?

No. Turning an existing business into a SaaS or building a completely new idea from scratch are both possible; in either case the starting point is the same field-tested multi-tenant core.

Does performance drop as tenant count grows?

The architecture is built to prevent this: caching (Redis), containerization and monitoring mean that as tenant count grows, only the infrastructure needs to grow — the application logic doesn't change.

Can we adapt it to a new sector after launch?

Yes. The shared SaaS core adapts to a new vertical with sector-specific modules (bookings, stock, subscriptions and the like); every one of our 46 products came about exactly this way.

Let's build your SaaS idea on a field-tested core

We'll listen to your tenant model and plans and map out where to start, together. The first conversation is non-binding.