Skip to content
Locins
Book a call

Locins OS: Built like the big platforms. For every business.

Locins OS sits under every Locins Terminal. It connects the data from many systems, controls who sees what and shares it live with regions and partners.

Locins OS is the data platform under every Locins Terminal. A Gate per source, data in three layers (bronze, silver, gold), a runtime for Bricks, permissions with purpose and an audit log, sharing via OpenSharing. Multi-tenant, in the EU, on request as your own instance.

Book a callFor developersThe overview: Locins Terminal

Architecture

The building blocks of Locins OS.

Your systems dock on at the bottom, the data sits in the middle, Bricks run on top in your Look. Permissions and Locins AI reach through everything.

  1. GatesOne Gate per source: mirrored, live or shared. Only the Gate talks to the source, including the way back.
  2. Data in three layersBronze as delivered, silver matched, gold as ready answers. Every number knows its origin.
  3. Shared modelGuest, booking, property, payment and event based on schema.org.
  4. PermissionsLocins Pass for guests, roles for the team. Every grant has a purpose and an expiry, every access is in the audit log.
  5. BricksRead silver and gold, never the source. Versioned and reviewed by Locins.
  6. LookLogo, colours, type and pictures across website, app page, guest guide and screens.
  7. Locins AI and MCPEvery function of a Brick is also an MCP tool. The major models run in the EU.
  8. SharingGrants via OpenSharing, live, without a copy, with expiry and revocation.

Locins OS in seven steps.

  1. 1Today

    Your data sits in many systems: Airbnb, Booking.com, calendar, till, Excel, email. Nobody sees the whole picture.

    Isolated tools without a shared data model, double entry, booking conflicts, no reporting across channels.

  2. 2Your Terminal

    You get Locins Terminal with your business account. A Terminal can carry several projects, such as a holiday flat and a café.

    A Terminal is a tenant with its own data space, team, roles and its own MCP access. Projects share data and Gates, permissions apply per project.

  3. 3Gates

    Your systems connect. You change nothing and keep working as before.

    One Gate per source, mirrored (regular sync), live (fetched on demand, nothing stored) or shared (a partner shares via OpenSharing, no copy). Only the Gate talks to the source, including the way back.

  4. 4Data

    Your data climbs: in the valley as delivered, on the trail matched, at the summit as ready answers.

    Bronze with timestamps per source, silver as a shared model based on schema.org, gold as data products. The origin of every field is kept.

  5. 5Permissions

    Guests arrive with their Locins Pass, your team with roles. Who sees what is settled.

    OAuth 2.1 with PKCE, roles per project, SSO for large teams. Every grant is a record with purpose and expiry, every access is in the audit log.

  6. 6Bricks

    Bricks run on top: booking, check-in, guest guide, report. A Look gives everything your style.

    Bricks read silver and gold, never the source. Functions, rules, events and slots, versioned and reviewed by Locins. Every function is also an MCP tool.

  7. 7Sharing

    Many businesses, one foundation. You share what you want with whom you want: your region, partners, your AI.

    Grants from the summit via OpenSharing, live, without copies, with expiry and revocation. Match rooms compute together without showing raw data.

Three systems, one guest.

In the valley your data sits as it arrives. On the trail Locins sees: that is Mara three times. At the summit there is a ready answer.

Bronze is the unchanged copy per source with timestamps. Silver is a shared model for guest, booking, property, payment and event based on schema.org; AI suggests the field mapping, a person confirms. Gold are data products per Terminal and, only with consent, per region. Every number knows its origin.

When a match is uncertain, Locins asks you before two guests are merged.

Example

  • July: 27 of 31 nights booked

    from Airbnb and calendar

  • Guests from Bavaria, Switzerland and the Netherlands

    from Airbnb and guest list

  • Quiet from 3 to 14 November

    from calendar and Booking.com

Bricks

41 Bricks in five families.

Each Brick is a ready-made function with clear permissions: what it reads and what it writes. Bricks read silver and gold, never the source.

  • Guests18 Bricks

    • Booking
    • Check-in
    • Tickets
    • Table reservations

  • Team6 Bricks

    • Tasks
    • Entry
    • Table plan
    • Report

  • Data5 Bricks

    • Calendar
    • Occupancy
    • Guest origin
    • Stock

  • AI6 Bricks

    • Guest guide AI
    • Translate
    • Copy
    • Reply to reviews

  • Connection6 Bricks

    • In ChatGPT and Claude
    • Local tips
    • Neighbour tips
    • Sharing
All Bricks

One Look over everything.

The logo, colours, type and pictures of your business lie over every Brick. Same Bricks, a different face. One click.

All Looks
  • Preview in the Look Zitrone: a house by the sea with a lemon treeLook Zitrone
  • Preview in the Look Dolomitz: a chalet in front of rocky peaksLook Dolomitz

Locins AI and MCP

Every function is a tool for AI.

Every Terminal has its own MCP access. Your AI, such as ChatGPT or Claude, only sees what you release, and you can end the connection at any time.

  • Answers only from released data, with a source.
  • The providers' models do not learn from your data.
  • Booking and paying only with confirmation by a person.
  • Every AI answer is in the log.

Processing in the EU with training contractually excluded. Tool permissions per Brick, protection against injected instructions in guest messages, a log entry per call with Brick, model, version, source and grant.

Go to Locins AIFor developers

Share data live. Without copies.

You release it, the recipient sees it live: your region the weekly occupancy, a partner your free dates. Without names, revocable at any time.

Grants from the summit via OpenSharing, the open standard of the Linux Foundation and successor of Delta Sharing. Shared are tables, files, Agent Skills and models. Recipients read with their own tools, such as Iceberg clients, Python or their data platform, or with their AI agent.

Your Terminal

  • Data productWeekly occupancy
  • Data productGuest origin
  • SkillFree dates
  • Region BodenseeWeekly occupancyliveexpired
  • PartnerFree datesliveexpired
  • Own instanceown data platformliveexpired
  • A partner's AI agentWeekly occupancyliveexpired
Two frosted boxes touch, only a small cube in the middle is visible

Match room

In match rooms, businesses and the region compute together, for example how many guests also visited the museum. Nobody sees the other side's raw data.

Sign-in via Locins Pass or the recipient's own identity provider (OIDC), short-lived keys, every read in the log. Personal data is never shared raw, only aggregated.

For regions

Built open and secure.

Locins speaks open standards: OAuth 2.1 and OpenID Connect for sign-in, MCP and Agent Skills for AI, OpenAPI for interfaces, schema.org for readable data, iCalendar for calendars, OCTO for tours and activities, OpenSharing and Apache Iceberg for sharing.

Export as CSV and JSON, data products also as Iceberg tables. The Locins API is published as an OpenAPI file.

  1. Locins runs in data centres in the EU. On request there is a dedicated instance in Germany or Switzerland.
  2. Every business has its own data space. No business sees another's data.
  3. Sign-in with OAuth 2.1 and PKCE, SSO via SAML or OIDC.
  4. Every access is in the audit log: who, what, when and why.
  5. TLS in transit, database encryption at rest, automatic backups.
  6. We process your guests' data on your behalf, under a data processing agreement per GDPR.
  • OAuth 2.1Sign-in
  • MCPAI
  • Agent SkillsAI
  • OpenAPIInterface
  • schema.orgData
  • iCalendarCalendar
  • OCTOTours
  • OpenSharingSharing
Trust and securityAll Gates

Common questions.

Who owns the data?

You do. Locins processes it on your behalf.

Can I take everything with me?

Yes, completely, at any time and in open formats.

What happens if I leave?

You take your data with you, then we delete it within the periods in your contract.

For every business. Complex requirements too.

For every business

  • Ready to start right away.
  • Each business in its own data space, all on the same foundation in the EU.
Create account

Your own instance

On request
  • For complex requirements, on request.
  • Same code, own database, own sign-in, own domain, your brand.
  • Data location EU, or Germany or Switzerland on request.
Book a call

Separate database and own keys, SSO via your identity provider, data products via OpenSharing straight into your data platform, without copies.