Skip to content
Locins
Book a call
For brands and groups · on request

Your brand. Your locations. One terminal.

A hotel group, an outdoor brand with stores or a mountain railway with a festival: Locins Terminal under your name, on an instance of its own.

Book a call

On a call we show you Locins Terminal live.

Example

Three layers: the Locins OS foundation at the bottom, an instance of its own on top, and a phone, laptop and card above

An environment of your own. The same code.

Your Terminal runs on its own instance of Locins OS, the foundation under every Locins Terminal: its own database, its own sign-in, its own domain.

Location

In the EU, in Germany or Switzerland on request.

Brand

Website, guest guide, check-in and customer card in your Look, with your colours, your typeface and your name.

Updates

Every improvement to Locins reaches you too, in a time window you set.

How Locins OS works

Every location. A single Terminal.

Each location is its own project in your Terminal, with its own team, package and permissions. Head office sees them all together.

Bricks, the building blocks for your business, bring the tools.

  • Click and collect
  • Membership card
  • Tours
  • Rentals
  • Check-in
  • Reports
See all Bricks

Your systems stay. Your data flows back.

Locins connects to what your head office uses: ERP, tills, CRM, online shop, booking system.

Whatever is created in Locins, you share live into your own data platform. No copies, no exports.

Technical

Connected through Gates, mirrored or live. Sharing uses OpenSharing, the open standard of the Linux Foundation: data, files, models and agent skills, meaning abilities for AI agents such as “check availability”. With purpose, end date and withdrawal, and every access logged.

All Gates

AI on your terms.

The large models run through Locins AI, the secure AI layer of Locins, in the EU, in Germany or Switzerland on request.

You decide which data each AI may see. The providers' models do not learn from your data.

More about Locins AI
A base plate with slots holding small building blocks for AI models

Your team signs in the way it always does.

  • Single sign-on

    Through your identity provider via SAML or OIDC. You manage access where you already manage it.

  • Roles per location and department

    The Innsbruck team sees Innsbruck, head office sees everything.

  • Shares

    With purpose and end date, for data going in and going out.

  • Audit log

    Every access and every AI answer is recorded.

  • Separate data

    Your instance shares no database with anyone else.

  • Customers with Locins Pass

    One account for your brand and every place on their adventure.

The data processing agreement, technical and organisational measures and the list of subprocessors are available on request. hello@locins.com, subject “Dokumente”

Trust and security
A bright outdoor store with jackets and backpacks in long rows

Three steps to your Terminal.

  1. 01

    Conversation

    What you need, what you already have, who needs a say.

  2. 02

    Set-up

    Our team sets up your instance, connects your systems, moves your data and designs your Look.

  3. 03

    Launch

    First at a few locations, with training for the team. Then everywhere.

Common questions.

Do we need our own development team?

No. We build it with you. If you have a team, it can build along: via the SDK, APIs (described as OpenAPI) and MCP.

Can we take everything with us?

Yes. All data can be exported at any time, and whatever you share via OpenSharing is readable in your platform anyway.

Can we build our own Bricks?

Yes. Your own Bricks run only in your instance, or go into the catalogue after review.

Tell us what you have in mind. We reply within two working days.

Book a call