sota Enterprise

Your experts build the apps. Your company sign-in decides who gets in.

The people who know the work build their tools with AI and put them live themselves, on your own server in Germany, behind your Microsoft 365 sign-in. They ship updates without a ticket and never deal with servers, backups or certificates. IT decides who may open which app.

Example access list: which person may open which app
Personsalesshiftsboard
Managing directormay openmay openmay open
Sales leadmay openno accessno access
Shift managerno accessmay openno access
Team assistantNew request
ApproveBlock
Example: who may open which app. A new colleague shows up as a request until you decide.

Built by the people who know the work, run where IT can see it

For the expert who builds the app

  • You build the tool your team needs with Claude, Cursor or any AI assistant.
  • You say “deploy my app”, and it is live at its own address, already behind the company sign-in.
  • You ship the next version yourself, the same way, whenever it is ready.
  • No servers, certificates, login code or backups to look after.

For IT and management

  • The tools your teams build stop living on laptops and in chat threads.
  • The apps and their data run on a server that belongs to your company alone, in Germany.
  • People sign in with the Microsoft 365 account they already have.
  • You see who has access to what, and you can take it away in one place.

What happens when a colleague opens an app

  1. 1

    A colleague opens the app

    For example sales.yourcompany.sota.io, from a link or a bookmark.

  2. 2

    Microsoft 365 asks who they are

    The normal company sign-in. sota never sees the password.

  3. 3

    The first time, a request appears

    The person waits on a “request sent” page and does not see the app.

  4. 4

    You approve and pick the apps

    In the sota dashboard: approve or block the person, then tick the apps they may open.

  5. 5

    They are in

    From now on the app opens straight after the Microsoft sign-in.

What sota runs for you

The parts that usually stop an internal tool from going live are handled by the platform, for every app.

Servers
Your apps and their databases run on a server of their own, used by no other customer. We set it up, patch it and watch it.
Addresses and certificates
Each app gets its address under your company name, such as sales.yourcompany.sota.io, with HTTPS from the first minute.
Sign-in
Every app is behind your Microsoft 365 sign-in automatically. There is no switch to forget and no login code to write.
Databases and backups
Each app can have its own PostgreSQL database. It is backed up every night, and the backups are kept for seven days.
Isolation
Every app runs in its own sandboxed container (gVisor), so one app cannot take over the server.
Builds and rollbacks
sota detects the framework, builds the app, switches traffic only when the new version answers, and can go back to the previous version.

Updates without a ticket

The person who built an app keeps improving it. They ship a new version from their AI assistant, from the terminal or through the API, using the API key you gave them. The address, the sign-in and the access list stay as they are.

If a new version does not start, the old one keeps running. If it starts but is wrong, they roll back to the previous version.

$ sota deploy

Deploying sales...

Uploading... done

Deployed to https://sales.yourcompany.sota.io

# Same address, same sign-in, same people with access.

IT keeps control

Speed for the people who build, and an overview for the people who are responsible.

Your own server, in Germany
Used by no other sota customer, hosted at Hetzner in Germany. The apps, their databases and their backups stay in Germany; so do the builds and the sign-in service, which run on the shared sota platform.
Who may open which app
One list in the dashboard: every person who has signed in, their status, and the apps they may open.
One place to revoke
Block a person or take away one app. It takes effect within a minute, also for people who are signed in right now.
Keys that can deploy, not decide
Builders get their own API key from you, named and revocable one by one. A key can deploy, roll back and remove apps, but it cannot change who has access, create or revoke keys, or change billing.
Only what is needed from Microsoft
sota receives a person’s ID, name and e-mail address. It cannot read mail, files or calendars in your Microsoft 365.
A contract IT can sign off
A signed data processing agreement (Art. 28 GDPR), the service level and the support we give are part of the Enterprise contract.

Available now, and what comes next

Available now

  • Own server per company, in Germany
  • Microsoft 365 sign-in in front of every app
  • Access requests, approve or block
  • Access per person and per app
  • Apps at <app>.<yourcompany>.sota.io
  • Database per app with nightly backups
  • Deploy by AI assistant, CLI or API

Coming next

  • Guided Microsoft 365 set-up in the dashboard (until then we do it with you, about 15 minutes)
  • Your own domains, such as tools.yourcompany.de

Not yet

  • Google Workspace sign-in: Microsoft 365 only for now
  • Apps cannot send e-mail through sota yet
  • Roles inside an app (an app sees who someone is, not their role)
  • Public endpoints: every address of an app is behind the sign-in, so outside services cannot call in

Read the details

Talk to us

Tell us which apps your teams want to run. We set up your server and the Microsoft 365 sign-in with you.

Write to info@sota.io