Samna brings the systems and protocols your buildings already run into the way you work with AI today: API first, MCP, command line tools and access control.
The old and the new, working as one
Buildings run on systems and protocols from long before AI, while work now starts in an AI chat. Samna is the enabler in between: it brings what you already run into the way you work today, safely and on your terms.
Everything you run, in one place
Panels, screens, sensors, locks, rooms, appointments, orders, calendars and people meet in Samna, together with your business logic and every integration in and out. The technology and protocols you already have keep working, our built in access control governs all of it, and your AI reaches it where you already work, never seeing more than you choose to share. These are only examples: whatever your building runs can join.
Devices, rooms, calendars, people, business logic and integrations connected to Samna in the middle
Doors and locks
Lockers and chargers
Rooms and desks
Free, busy or held at the door
Signage in lobbies and halls
Temperature, air and presence
Who may enter, and when
Booked, opened and charged
Pool cars and parking
Everything that can be booked
Microsoft 365 and Google
Portals in the browser
Book and open on the go
Employees with their own access
Guests who come and go
Flows, rules and scripts, always yours
Old systems and protocols, in and out
Times booked with people
Food, supplies and services
Connect reaches anything, both ways
Samna Connect talks to the systems that are hard to talk to, in both directions. It reads from them and calls them, hides the difficult protocols, keeps the secrets and the access to them, and measures every call. What it reaches comes out as one clean, secure API and MCP server with unified access control, and it feeds the whole Samna stack: Bookable, Sync and Sign.
Sensors, REST APIs, MCP servers, MQTT, webhooks and databases connected both ways to Samna Connect, which serves one API and MCP server and feeds Bookable, Samna Sync and Samna Sign
Explore Samna Connect
API + MCP
One secure API with unified access control
Sync handles your business live
What needs to be transformed, mapped and edited, Samna Sync does as it happens, so your business cases run live: into Bookable, onto Samna Sign screens and back to the systems you already run.
Azure and Google flowing into Samna Sync, whose mapper maps each calendar out to Azure, Google, Samna, Samna Sign and your own system
Explore Samna Sync
Microsoft 365 calendars
Google Workspace calendars
Fields shaped on a graph
Written back to the source
Written back to the source
Bookings in Bookable
Shown on screens
Your own system
Bookable aligns the day
Most of the day to day comes down to aligning time between people, services and assets. That is the very core of what Bookable does, and every booking shows up on Samna Sign screens and reaches the people it concerns.
Booking events and requests coming in through Samna Connect to Bookable, going out through Samna Connect again, through Samna Sync and on to the end user
Work starts in a chat
Many people now open the day in an AI chat.
They lay out a plan, pick up where they left off, or, where it is allowed, work through email, messages and task lists. The desktop has changed, and so has the way we work and the way work gets enabled. This new wave of technology is only speeding that up, and the systems around a workplace have to keep pace with it.
API first, every time
Every Samna solution is an API before it is a screen.
The portals use the same API you do: one envelope, the same paging, filtering and errors, described in OpenAPI. Whatever you build, script or ask your AI to do runs on the foundation the portals run on, so nothing is held back for our own screens and nothing you make breaks when the screens change.
An MCP layer for your AI
Every Samna service serves MCP, so your assistant connects to Samna like any other connector.
Add Samna to Claude as a connector and it calls the same operations as the portals, under the same rules. Ask for a free room, move a booking or check a synchronization, and every step streams back as it runs. Hosts that draw MCP apps show the run as it happens, so you see exactly what the AI did on your behalf.
Command line tools for people and machines
Each solution ships its own cli, and every cli speaks the same way.
book, ssync, scon and sauth share one shape: the verbs get, create, replace, update and delete, a login sent to the service itself, and output that reads well in a terminal and parses cleanly in a pipe. They are written to be read by AI and used by developers alike, every cli serves its commands over MCP, and each carries a skill that teaches an agent how to drive it.
One set of rules, from portal to chat
Our built in access control governs every call, from the portal to the chat.
Your AI never reaches more than what you share with it, or already trust it with today. The same claims decide what a person sees in a portal and what their assistant may read or change, so handing a task to the AI never opens a door you have not opened yourself. Every write is recorded in the audit log, whoever made it.
Build with your AI, safely
When you want the AI to build with you, it works inside a sandbox.
Every step of a flow is a Tengo script that runs sandboxed, and our workflow engine nimflow ties the steps together. That lets the AI safely put together new integrations, synchronizations, booking triggers, payment flows, heating controls or whatever should happen when something changes in your Samna instance. Each flow stays simple enough for both of you to read, and you correct or rework it from the chat or in our portals.
Changed while you are still on the call
The guard rails put no limit on what you can create.
Your IT department no longer needs long running tickets or deep investigations into bugs, because the framework is already in place and the sandbox lets nothing break: what you see is what you get. Processes that used to be slow become fast. A change to a business flow can be made, tested and safely rolled out while you are still on the phone with the other department, or you simply make it yourself.
Yours to take
Your business logic lives in Samna, but it always belongs to you.
Flows, rules, scripts and data are easy to export and set up elsewhere, on your own servers or another platform. We would rather earn your stay than hold you to it. Samna is here to enable you, not to lock you in.
An AI chat asking Samna for a free room and booking it
Find me a free room for six at two and book it.
Fjord room is free at 14:00 and seats eight. It is booked for you until 15:00.
Screenshots of Claude Desktop, Claude Code, Codex and ChatGPT
An API request for bookables and its json answer
Samna added to Claude as a connector, with its tools listed
Samna Bookable, MCP connector
The book cli listing bookables, creating a booking and serving MCP
What your AI may and may not reach in Samna
What your assistant can reach
Rooms on your floor
Your own bookings
Calendars shared with you
Billing and secrets
Anything you cannot see yourself
A flow of a trigger, sandboxed business logic and an action
Heating on, door opens
A flow changed, tested and rolled out during a phone call
On the phone with facilities
Flow changed in the chat
Tested against today
Rolled out to every building
Your actions, code, business logic, rules and data exported from Samna
Actions and flows
Code and scripts
Business logic and rules
Examples made with Claude Design from connected data
Proposal one pager
Campaign proof sheet
Behind every building are protocols and systems from long before AI. Samna brings them into the new way of working.
What comes in rarely fits as it is. It has to be shaped on the way.
And when time, people and places line up, the day starts to run itself.
Reads and calls, both ways
Connect pulls data in and calls out to the same systems, so a booking can open a door and a sensor can move a booking.
Difficult protocols hidden
MQTT, building protocols, brokers, streams and odd APIs are optimised and wrapped once, so nothing else has to speak them.
Secrets and access managed
Connection strings and tokens are sealed, access to them is governed, and expiring credentials raise an alert before they fail.
Metrics on every call
Traffic, duration and errors are measured per connection, with rules that warn when something drifts.
One secure API and MCP
Everything comes out as one versioned REST API with its OpenAPI document and an MCP server, under the same access control as the rest of Samna.
Mapped on a graph
Node flows on the nimflow engine shape every field from one system to the next.
Redacted by claims
What each person may see decides what is synced and what stays hidden.
Calendars you already run
Microsoft 365 and Google Workspace into Bookable today, with writeback to the source on the way.
Rooms, desks, cars, services and people, each with its own rules.
Actions on every step
Tengo actions and webhooks run when a booking is made, moved or ends.
Pays and opens
Adyen and Stripe take the payment, Salto opens the door.
Claude Desktop, Claude Code, Codex, ChatGPT, a terminal and the portals reaching Samna: the API goes out from Samna, the command line and MCP stand on it, the command line also serves MCP, and MCP connects your AI apps
How you use it
Whether you are a system administrator, a developer or a small business owner, you stay in control and use the Samna ecosystem from wherever you already work. We love integrations, so instead of building an assistant of our own, Claude Desktop, Claude Code, Codex, ChatGPT or your own terminal connect to Samna directly. We believe a stack that both you and your AI can work with, understand and trust with your workflow is the key to joining the old with the new.
Connectors in your desktop AI
In ChatGPT and Claude Desktop, Samna appears as a connector. Add it once, sign in, and your assistant can read and act in Samna with exactly the access you have.
MCP straight into your terminal
In Claude Code, Codex and other terminal agents, the Samna MCP server is added directly. The same tools sit next to our command line tools, so developers and their agents work from one place.
One layer in a stack you already trust
Anyone can build almost anything now, and that is exactly why what it stands on matters. Compliance, security, maintainability, ease of use and reuse count for more than they ever have.
The frames and platforms made for a slower way of working were never designed for software that anyone can write in an afternoon. Samna does not ask you to replace them.
It is one layer in a stack you already run, between your cluster and your applications, so it stands on the same compute, containers, orchestration, observability and data your infrastructure already trusts.
Guard rails at both ends
Free in the middle
Try ideas, build flows and change them as often as you like, from your AI chat, your code editor or the portals. Every step is business logic that runs sandboxed, so your AI can safely put together integrations, synchronisations, booking triggers or heating controls, and each flow stays simple enough for both of you to read and correct.
A typical Kubernetes stack for a large organisation in Azure, built up as a pyramid from network and compute through containers, Kubernetes, observability, data and the API gateway to Samna and the applications
Your solutions, services and integrations
Security, deliverability, scalability and compliance
Business logic, scripts and your AI, free to explore
Most business work comes down to presenting, transporting or converting data. In Samna every one of those operations passes the same safeguards on its way in and on its way out.
Between the two ends you and your AI are free to work. Nothing made there can reach past the guard rails, so experimenting stops being a risk.
The chain from service through Samna safeguards and AI work back through Samna safeguards to service
Azure API Management
Data and messaging
Azure Database for PostgreSQL
Containers and security
Network and compute
Settled before and after
Security, deliverability, scalability and compliance are settled before the work starts and checked again before anything leaves. Your AI gets just the right tools for the job, so whatever it builds is easy to evaluate.
Service to Samna, Samna to AI work, AI work to Samna and Samna to service. That chain keeps every result inside the space you work in, and it is the baseline we believe tomorrow’s platform needs.
Claude Design and dashboards on your live data
Point Claude Design at Samna and it designs with what is really happening in your buildings. Bookings, occupancy, devices and the systems behind Connect become one pagers, dashboards and campaign assets in minutes.
Explore Claude Design
Samna connected through MCP to Claude Design
Live data, your access
Samna is connected as an MCP server, so Claude reads only what your access allows and every number it shows comes straight from the source. Ask for a weekly occupancy report, a dashboard for the facilities team or a proposal built on real usage, then refine it in the chat.
Deploy what you make
With Samna in the loop, the dashboards and designs you create with your AI tools can be deployed and used safely across your organisation. They run on live data behind the same access control, so everyone sees only what they are allowed to.
Go to the developer page
Go to Samna Auth
Go to Samna Sync