sota Enterprise overview

sota Enterprise runs the apps your people build on a server that belongs to your company alone, and puts every app behind your Microsoft 365 sign-in. Only colleagues you approve get in, and you decide per app.

The parts

PartWhat it is
Enterprise accountOne normal sota.io account (one e-mail address) that owns the apps, the server and the access list. You sign in to the dashboard with it.
Your serverA server used only by your company, hosted at Hetzner in Germany. Your apps and their databases run on it. sota sets it up when you start. Builds and the sign-in service run on the shared sota platform, also in Germany.
Your company nameA short label such as yourcompany. Every app gets the address <app>.yourcompany.sota.io with HTTPS.
sota AccessThe sign-in in front of every app. It sends people to your Microsoft 365 sign-in and checks, on every request, that the person may open this app.
PeopleEveryone who has signed in to one of your apps at least once. Each person is pending, approved or blocked.
GrantsWhich approved person may open which app.
API keysKeys you create for the colleagues who build and update apps.

How a colleague gets in

  1. They open an app, for example https://sales.yourcompany.sota.io.
  2. sota sends them to the Microsoft 365 sign-in of your organisation.
  3. The first time, sota records them as a pending request and shows "Request sent". They do not see the app.
  4. In the sota dashboard you approve or block the person and tick the apps they may open.
  5. The next time they open a granted app, they are in. An app they have no grant for shows "No access".

A session lasts at most 8 hours and ends after 1 hour without activity. Then the person signs in with Microsoft again, which is usually a single click.

Taking access away

  • Block a person: they lose access to every app, including sessions that are open right now.
  • Remove a grant: they lose access to that one app.
  • Revoke an API key: the key stops working for deploys.

Changes reach the sign-in within a minute.

Who can do what

ActionDashboard sign-in (owner)API key
Create, deploy, update, roll back and remove appsyesyes
Approve and block people, change grantsyesno
Create or revoke API keysyesno
Change billingyesno

So a colleague with a key can ship updates on their own, but cannot change who has access.

Deploying and updating apps

Enterprise apps are deployed like any sota app: from an AI assistant over MCP, with the CLI or through the API. Each deploy builds a new version and switches traffic only when it answers its health check; the previous version can be restored with a rollback. The address, the sign-in and the grants stay the same across deploys.

Each app can have its own PostgreSQL database on your server. It is backed up every night, and backups are kept for seven days. Restores are done by the sota team on request.

Getting started

  1. Talk to us. We create your Enterprise account, your server and your company name.
  2. Your Microsoft 365 administrator registers one app in Microsoft Entra ID: Set up Microsoft 365 sign-in. For now we do this step together with you; a guided set-up in the dashboard comes next.
  3. Deploy the first app, open it, and approve yourself and your first colleagues.

Read on: identity headers for your app and known limits.