Answers to common questions about Samna: the solutions, hardware, integrations with Exchange and Google, security, privacy and how to get started.
Write to hello@samna.io, call +47 4612 4712, or use the contact form on this site. Tell us a little about your buildings, the systems you have and what you want to solve, and the right person on the team will get back to you.
Developers can also start on developer.samna.io and the developer page, where the APIs, the command line tools and the MCP servers are documented.
Yes. Send a message through the contact form or to hello@samna.io and tell us which solutions you are interested in. We tailor the demonstration to your case, whether that is booking rooms and desks, signage in the lobby or the integrations behind them.
In the demonstration we show the portals, the devices and the developer tools, and walk through how Samna would fit with the systems you already have.
Samna is based in Oslo, Norway, at Lilletorget 1. You are welcome to visit; get in touch first so the right people are there to meet you.
The Samna cloud runs in Azure's Norway East and West regions, with datacenters in Oslo and Stavanger, so your data stays in Norway as well.
Samna means to gather, and that is what we do: we gather your applications and integrations in one place, at any scale. The team behind Samna has spent years building infrastructure and integration solutions, and Samna is that experience and expertise turned into software. It lets you gather, enable and govern your integrations and external connections in one place, keep stale data in sync, and move and transform data between any two points you choose, safely and in a way AI agents can work with.
On top of that, Samna is a digital signage and booking platform, and working with time and schedules is our expertise. The ecosystem ties it all together: it brings your data to the signage screen with little effort, and carries the booking flow through to access cards, desk control and the other building integrations an office needs, in the office as well as out in the field.
The mantra behind Bookable is make everything bookable, and that is our aim: to help everyone who deals in rental or booking take control of their assets and resources, and present them in a bookable way.
No. Every Samna solution works well on its own: Bookable for booking, Samna Sign for digital signage, Samna Connect for integrations, Samna Sync for calendars and legacy systems, Samna Auth for sign in and access, and Samna Device Management for the hardware. Pick the one that solves your problem and leave the rest until you need it.
Together they form the Samna ecosystem, and that is where they shine. A booking made in Bookable appears on Samna Meet and Samna Sign without extra integration, Samna Connect brings outside data onto the same screens, and Samna Auth governs who may see and change what across all of them.
Moving to Samna, or away from it, is just as straightforward. Every solution is API first with its own documented API, and Samna Sync carries your data over when you migrate. You keep ownership of your core business logic, and use our platform and ecosystem for everything around it.
Yes. Samna delivers its own devices with the software on them: the Samna Meet room panel outside the meeting room, the Samna Area box that turns any TV into a signage screen, and Samna Reflect, a mirror with a display behind the glass, coming soon. Every unit is enrolled and kept up to date through Samna Device Management.
We also believe in reusing what you already have. The Samna Sign Engine turns screens and players you already own into Samna Sign units, so old screens get a new life as signage instead of ending up as waste. The whole lineup is on the devices page.
That is our end goal. Every solution is built to run self hosted on your own servers, with the same features as in the Samna cloud.
For now every solution runs in the Samna cloud, hosted in Azure's Norway East and West regions, so that we can guarantee your safety while the platform completes its security reviews and compliance testing. Follow the way there on our roadmap.
Yes, and we recommend it. Start where the need is greatest: Bookable when rooms, desks or resources are hard to find and book, Samna Sign when screens need fresh content, Samna Connect when systems need to talk to each other, or Samna Sync when calendars and legacy systems drift apart. Whatever fits your need and solves your problem is where you should start, and one building first is a fine scope.
Add the rest when you are ready. What you add later already knows your buildings, people and rules, so nothing has to be set up twice. Get in touch and we will help you find the right place to start.
Your organization does. Access is governed by Samna Auth and its access model, claimius. Every service denies by default and checks every read and write against the access you have granted, across every organization and location you run. Grants can be limited in time, and every change to access is written to an audit log in the same transaction.
Sign in follows open standards: OAuth 2.0 with PKCE (RFC 7636), signed JSON Web Tokens (RFC 7515, RFC 7517, RFC 7518, RFC 7519) with per app signing keys and key rotation, and OpenID Connect logout. Sender constrained tokens with DPoP (RFC 9449) and mutual TLS (RFC 8705), pushed authorization requests (RFC 9126) and the FAPI 2.0 security profile are partly in place and being completed. A security audit of sign in and access control is on our roadmap.
The contact form stores the name, email address, company, phone number and message you send, so that we can answer you. Company and phone number are optional, and what you send is used for nothing other than answering you.
The message is stored in our database in Norway and is also posted to our team's Slack channel, so the right person sees it quickly. This site loads no third party scripts, fonts or tracking pixels, and every connection is encrypted, with HTTPS enforced through HSTS (RFC 6797). The full privacy policy has the details.
Yes. Write to hello@samna.io or use the contact form, and we will tell you what we hold about you, and correct or delete it on request, as articles 15 to 17 of the GDPR entitle you to.
All Samna data is stored in Norway, in Azure's Norway East and West regions. Our cloud provider holds ISO/IEC 27001, 27017, 27018 and 27701 and SOC 1, 2 and 3. Our own controls are aligned with ISO/IEC 27001, which is our target for certification, and data minimisation and privacy by design (GDPR articles 5 and 25) guide how every service is built, with field redaction so people see only what they are allowed to see. The full privacy policy has the details.
Inside Samna Connect. Every key, token and password for an integration is sealed with AES-256-GCM before it is stored, is masked whenever it is shown, and is unsealed only to call the system it belongs to. When a vendor issues a new refresh token, Connect rotates it into the sealed secret by itself. Platform keys are kept in Azure Key Vault on FIPS 140 validated modules.
Connect also watches every credential it holds: certificates, JSON Web Token expiry, dated secrets and API keys. It notifies you 30, 14, 7 and 1 days before a token or certificate expires, through Teams, Slack, email or a webhook, so an integration never stops by surprise. Connections to outside systems use OAuth 2.0 (RFC 6749), JWT bearer assertions (RFC 7523) and TLS 1.3 with client certificates (RFC 8446) where the vendor supports them.
Yes. Samna Sync keeps Microsoft 365 and Google Workspace calendars in step with Samna, so people keep booking rooms from the calendar they already use, and the booking shows up in Bookable, on Samna Meet and on Samna Sign screens.
Samna Sync also helps you migrate from on premises solutions, and keeps Samna in sync with legacy and older systems for as long as they stay in use. If you are stuck with OHIP, OPERA FIAS, HTNG, EWS, SOAP or other specific protocols otherwise not present in your stack, Samna Sync is your friend.
Yes. Samna Sync keeps your calendars, rooms and people in step with Samna, including services locked to one vendor, and carries the data over when you migrate. The mapping runs as flows you can read and change, so the rules for what goes where stay yours.
Samna Connect brings everything else into the same model: other APIs, sensors, brokers and building systems. Each system is connected once, its data is stored in one place, and from there it serves every Samna solution, a dashboard or your own code. You keep the systems that already work, and Samna makes them work together.
Every resource in Bookable can carry a QR code, with NFC chips planned. Scanning it opens the resource straight away, so people can book it, check in or see when it is free, and the same code can trigger a Bookable action or an integration.
Outside a meeting room, the Samna Meet panel shows whether the room is free and lets people book, check in or extend a meeting right there. The same booking reaches the Samna Sign screens in the lobby and can open the door through access control such as Salto, so the room is ready when people arrive.
Web APIs such as REST, GraphQL, gRPC, SOAP, webhooks and WebSockets, brokers such as MQTT with Sparkplug, Kafka, AMQP and NATS, building protocols such as Matter, Zigbee, BACnet, Modbus, KNX, OPC UA and LoRaWAN, and data sources such as SFTP, SQL, CalDAV, LDAP and SCIM.
And the list goes on. Every connector, with the transport and the authentication it uses, is in the Samna Connect technical docs, and the Samna Connect page gives the overview.
Yes. Every Samna service is API first, so what you can do in a portal you can also do through the API. Your developers script against it, and your own systems integrate with it directly.
AI agents can work with Samna through the API and over MCP, the Model Context Protocol. Even better is the command line tool on your own computer: the core applications each ship one, and it also runs as a local MCP server. The agent then works through your own signed in session, inside exactly the access you grant it, and no key has to leave your machine. That is extra safety on top of the access control every service already enforces.
Yes. Samna Connect runs as a standalone service with its own keys, its own portal, its own API and the scon command line tool. You can use it as the integration layer for your own products without touching anything else in Samna.
Together with Samna Auth, access follows your tenant: the people and machine clients you already manage there get exactly the access to connections and data you grant them. And when you add Bookable or Samna Sign later, the data Connect already collects is ready for their screens and actions.
Questions and answers
What people ask before they choose Samna.
No questions match that search.
Did not find your answer?
Ask us directly. The question goes straight to the team, we read every message ourselves and answer by email as soon as we can.
What you want to know about Samna, your spaces or the systems you run.
Thank you. Your question is with the team, and we answer you by email.
The question could not be sent. Please try again or write to hello@samna.io.