Hotels, tour operators, DMCs and cruise lines run on incompatible systems and move their operational data by email, spreadsheet and fax. Ananas GDS is the distribution layer that connects them today — and is becoming the system they run their business on.
data models in production code
live backend modules
automated tests, green
live environments — production and test
Fact sheets, stop sale and allotment, photos, a full rate-contracting Pricing Engine, a permanent rooming ledger, partner messaging, invoicing, e-invoicing, DMC Operations, PMS connectors, webhooks, an MCP server for AI tooling, and more — see the complete live feature list .
A Destination Management Company is a commercial party, not just a logistics desk. Ananas GDS runs a mandate-based contracting and fee engine for the hotel and tour-operator relationships a DMC sources, plus a full operational suite for transfers, fleet, dispatch, and excursions. See the DMC page.
One authority record per hotel, per tour operator. Principal: the DMC contracts the hotel and resells with its own margin. Agent: the DMC manages an existing hotel–operator contract and earns a fee instead — the platform won't let a markup appear where the DMC isn't in the price chain.
Four fee mechanisms on one engine, resolved most-specific-first by partner and operation type, with an immutable ledger recording exactly which rule produced which charge. Ananas never touches or settles the money.
A transfer ledger with movement and delay tracking, plus a fleet and crew registry that blocks a dispatch when a vehicle document or driver certification has expired — not just a reminder, an actual block.
A dispatch and assignment board with conflict detection, arrival and departure manifests, meet-and-greet coordination, and printable driver/guide day sheets for staff who never get a platform login.
Excursion operations run as a rooming-list-style ledger, backed by a local supplier registry — the same operational discipline Ananas already applies to hotel rooming and allotment.
Hotel → DMC → tour operator data flows through configurable relay modes — pass through, block, override, or anonymize — with provenance stamped on every relayed record.
Built after studying how established hotel PMS and tour-operator systems run day-to-day operations — every module additive, with not one line of the live platform modified. The reporting layer reads across both the original platform and this new layer at once.
Reference data, property portfolio, document & branding studio.
Units & condition, housekeeping, maintenance, stay restrictions.
Group blocks, sales desk & CRM, sales operations, agent commissions, budget & forecast.
Function spaces, event diary & BEOs, catering and menus.
Operations logbook, lost & found, destination calendar.
Report Builder — 20 queryable subjects across both platform generations, charted, 5 export formats. Daily Analysis — 13 automated checks that show their arithmetic, not a black-box score. Rules & alerts, integration control, an app store, and a second AlpineBits server endpoint.
Tour operators keep asking the same question: does it do what my core system does? Ananas Core is planned to be the answer — a system an operator can run their whole company on, built on supply data that is already inside the platform. It is not built yet; this is the direction, not a release date.
Catalogue, supply and charter-flight inventory; pricing schemes, promotions and dynamic packaging; quoting, a storefront, and two-way channel distribution.
Booking files, travelers, amendments and complaints; deposits, package P&L, and supplier payables.
German statutory obligations — jurisdiction-scoped from day one, not retrofitted for a market built elsewhere.
Strictly additive by design: Ananas Core would read the existing platform through one-way adapters and write only to its own database — the same discipline that has delivered every module so far without a regression to what's already live.
Every phase is scoped to end in a demonstrable outcome, so the programme can be re-scoped at any of eleven defined points rather than discovered late.
Licence, database, the price handover proven on real contracts.
Catalogue and supply; hotels appear as sellable product with zero re-keying.
The pricing scheme, promotions, and the repricing engine.
Hotel, transfer, and activity assembled into one priced package.
Branded, priced, day-by-day itineraries.
Booking files, passengers, amendments that recalculate.
Charter seat inventory and recorded flights.
Agent portal, storefront, channel distribution both ways.
German statutory duties, jurisdiction-scoped.
Deposits, package P&L, supplier payables, complaints.
Usage metering and verifiable commission billing.
Migrate off an incumbent system without stopping trading.
Sequenced inbound-first: the DMC and Pricing Engine modules already live cover much of the inbound case, so the first working system arrives sooner, on assets we already own.
You load your contracted product and the system prices what it owns. Managing that master data is the job.
Assemble packages from live third-party feeds. Infinite product — and since you own no inventory, your margin is someone else's price.
Put product in front of resellers. No accounting, no contracting, no operations — the core lives elsewhere.
All three assume the supplier is outside the software. Ananas GDS is the supplier's system. A new installation in any of the three categories above starts with an empty contract database somebody must key in by hand. An Ananas installation starts with the hotels already inside it, maintaining their own data. That starting position is what the other twenty-five systems we analysed cannot copy — they can build features; they cannot build a supply side that's already populated.
Competitors start with an empty contract database. We start with hotels already inside the platform, maintaining their own rates, stop sale, and allotment.
Insolvency certificates with booking documents, statutory pre-contractual information before a traveler commits, lawful price-change rules — built in from the start, not templated on afterward.
Hotels, tour operators, and DMCs already share contracts and permissions here. Capabilities that need a bilateral integration elsewhere are a permission setting for us.
Twenty-three additional modules delivered without modifying a line of the existing platform. Every phase is gated on a demonstrable outcome, verified against real data before it's called done.
Honest about the risk: Ananas Core is a multi-month programme against entrenched incumbents with decades of head start. The phase gates above exist precisely so scope can be reconsidered at eleven defined points, rather than discovered late.
Today: a live data distribution platform, free to start, with real hotels, DMCs, and connectivity into the systems operators already run. Next: the V2 property-management layer, and Ananas Core. Come build it with us.
