Pilot build · v0.1 · Antalya → Europe

Not software.
An operating system
for your operation.

MindOps OS is the config-driven platform European tour operators and DMCs run on. Ship a new module in hours instead of months. Describe it in plain language; we build the schema, the grid, and the rules.

Book a demo See how it works

Pilot customers joining this quarter — no named references yet. Read the honesty note →

define → ship → run config.ts

> describe(
"transfer reservation module with pickup SLA"
)

generates

module: TransferReservation
schema: { pickupAt, driver, sla }
grid: AgGrid<Reservation>
rules: [commissionSplit, ...]
api: POST /transfers

SUPPLIERMARKETRELEASECOMM.

Alanya TRDE14d12%

Side HTLNL21d14%

Antalya XSE10d11.5%

01 / Contract matrix

Your contract matrix belongs in a grid, not a spreadsheet.

Every supplier, every source market, every release period. Agency contracts, hotel allotments, transfer rate cards. Model them as config and your team filters by market, season, or commission band without opening Excel. No more key-person risk when your contract manager goes on holiday.

[quote pending] "We moved 500+ agency contracts off Excel in one week."

agency_contracts · 517 rows

Market: DE, NL, SE +2 2026-S

Supplier Market Release Period Stop Sale Comm.%

Alanya Palace TR DE · SE 14 days – 12.0

Side Coast Hotel NL 21 days – 14.5

Antalya Transfer Co. DE · NL · SE 7 days active 10.0

Kaş Boutique Group DK 30 days – 13.25

Bodrum Yacht Partners DE · CH 45 days stop sale 9.0

İzmir Inbound DMC NL · BE 14 days – 12.75

schema-per-tenant · pg16 ag-grid enterprise

02 / Data layer

Enterprise data, from day one.

AG-Grid Enterprise for the grids your operators actually work in. PostgreSQL 16 with pgvector underneath. Schema-per-tenant for real cryptographic separation, not row-level security dressed up as isolation. AES-256-GCM encryption at rest. GDPR-aligned architecture your CTO can defend in a vendor review.

AG-Grid Enterprise pgvector AES-256-GCM Schema-per-tenant GDPR-aligned

[data sheet] Architecture diagram + schema-isolation explainer shipping at docs.mindops.net.

tenant_a

reservations

contracts

agencies

vouchers

aes-256-gcm

tenant_b

reservations

contracts

agencies

vouchers

aes-256-gcm

postgresql 16 · pgvector · rag

isolation is architecture, not policy

03 / Reservation flow

Hotels, transfers, tours. One tenant. One source of truth.

step 01

Contract

Supplier terms, allotments, release periods — modeled once.

step 02

Reservation

FIT, series, MICE — same model, filtered views.

step 03

Billing

Race-safe ledger. Two-phase payment reconciliation.

step 04

Voucher

Multi-language output. TR / EN / DE / RU live.

Stop reconciling three systems every night. Reservation, contract, operations, and billing run on one schema inside MindOps OS. FIT, series, MICE — same model, filtered views. Built for inbound operators selling into 5 to 30 source markets in EUR, USD, SEK, GBP.

[demo video] Two-minute walkthrough of a real reservation flow in the AG-Grid view — drops when first pilot lands.

04 / Module engine

Built for the team that changes twice a season.

When regulations shift mid-season or a new source market opens, your platform should not be the bottleneck. Describe a module in natural language; the config engine produces the schema, the forms, the grid, and the APIs. Our AI drafts the config; you review and publish. This is how "hours, not months" becomes how you work.

Soft claim · ships next quarter

Commission-rule authoring UI ships next quarter. Today you model commission structures through config and our team; the live rules engine lands with the next release.

mindops · module-gen

$ describe module

> reservation_import_module with xml source,
currency conversion, commission split

generating config

{
  "module": "ReservationImport",
  "source": { "type": "xml", "poll": "5m" },
  "fx": ["EUR", "USD", "SEK", "GBP"],
  "commission": {
    "split": "tiered",
    "bands": [0.10, 0.12, 0.15]
  },
  "schema": "tenant_a.reservations",
  "grid": "AgGrid<Reservation>"
}

✓ schema generated · ✓ grid generated · ✓ api generated

$ mindops deploy --review

Fit

Who this is for.

Mid-market tour operator

20–500 staff. 50–1,000 supplier contracts. 5–30 source markets.

Germany, Benelux, Nordics. FIT, series, MICE. Selling through B2B portals, GDS, agency networks. Legacy TO system is 12 years old.

Destination Management Company

Inbound to Europe. Complex contract matrices. Multi-market pricing.

10–100 staff. Thin-margin volume. Contract manager still running commission logic in Excel. Needs a turnkey pilot before a full rollout.

Travel-tech operator

White-label platform builders and niche travel SaaS.

You need a configurable back-end instead of a green-field build. Config-driven primitives, schema-per-tenant, AI module generator out of the box.

Not for: B2C online travel agencies, micro-agencies under five staff, and global chain hotels with group-level enterprise stacks.

Alternatives

How we compare.

No feature-counting. Change velocity is the category.

Alternative Where they fail MindOps OS

Legacy TO systems Rigid. Years-old UX. Every change is a vendor project. Config changes you control. Modern data stack.

Horizontal ERP 6–18 month implementation. Not travel-native. Travel primitives. Ship in weeks, not years.

Low-code platforms Fast to build. You build everything. Nothing is travel-aware. Contracts, allotments, release periods as primitives.

Custom dev Total control. Hiring, retention, scaling, six-month roadmaps. Standard platform. Spend your budget on your differentiation.

MindOps OS Config-driven. AI module generator. Schema-per-tenant. New module in hours. Enterprise data from day one.

Book a demo

Bring your real contract complexity.
We'll model it live.

Thirty minutes. A screen share. You name the mess — a multi-currency agency contract, a seasonal commission override, a release period nobody in your current system handles. We show you how MindOps OS treats it as config.

"No slideware, no canned demo tenant."

— how every mindops demo runs

Book a demo Read the FAQ first

FAQ

Before you book.

Where does the data live? Is it EU-resident? +

Default deployment is EU-resident (Frankfurt region). Schema-per-tenant means your data lives in its own PostgreSQL schema with AES-256-GCM encryption at rest. For paranoid deployments, a single-tenant VPC option is on the roadmap — ask in the demo.

What does pricing look like? +

We are in a charter-customer phase — pricing is per-pilot and negotiated. Expect mid-market ACV in the €30K–€120K/year range once general pricing lands. No surprise AI token charges; costs are capped and visible in-platform. Full pricing page ships when the first three pilots are live.

Do you have a named European reference customer? +

Not yet — first European pilots sign this quarter, named references land Q3 2026. Until then, we demo on a live MindOps tenant with real contract complexity, and we will introduce you to our Antalya-region inbound pilot for a peer-to-peer call.

What about GDPR / ISO 27001 attestation? +

Architecture is GDPR-aligned by design — schema-per-tenant, AES-256-GCM at rest, audit log by default, sub-processor list on request. Formal ISO 27001 certification is on a six-month path; happy to share the roadmap under NDA during vendor review.

How long does implementation take? +

Charter pilots run a non-critical line (e.g. transfer reservations or one supplier market) in four to six weeks. Full migration from a legacy TO system is scoped per customer — usually a quarter, not six months, because modules are config not custom code.

Not software. An operating system for your operation.