Known limits
What sota Enterprise does not do yet, and the risks we know about. We update this page when something changes.
Not available yet
- Guided sign-in set-up in the dashboard. For now sota sets up the Microsoft 365 sign-in together with you (steps). Coming next.
- Your own domains such as
tools.yourcompany.de. Apps run at<app>.yourcompany.sota.io. Coming next. - Google Workspace sign-in. Microsoft 365 (Entra ID) only.
- Roles inside an app. The app learns who someone is, not what role they have (identity headers).
- E-mail sending. Apps cannot send e-mail through sota. Use your own mail service if an app needs to send mail.
- Public endpoints. Every path of an app is behind the sign-in. Webhooks from outside services and scripts without a browser cannot reach an app.
- Self-service restore. Databases are backed up every night and kept for seven days; restores are done by the sota team on request.
- Runtime logs. You see build logs of each deploy; logs of the running app are not available yet.
- Organisation accounts. One sota account owns everything. Colleagues who deploy get API keys from that account, so the deploy history tells keys apart, not people. Give each person their own named key.
- Size. An Enterprise account runs up to 10 apps and 10 databases, each app with up to 512 MB of memory. Talk to us if you need more.
- New servers. Setting up a new Enterprise customer's server is done by the sota team, not from the dashboard.
Behaviour to know about
- Guests arrive as requests. People from other organisations who are guests in your Microsoft 365 tenant can sign in. They appear as pending requests like everyone else and get nothing until you approve them.
- New people wait for you. Nobody gets into an app before you approve them and grant the app. A person approved a moment ago may need to reload after up to a minute.
- Microsoft's sign-in comes first. If your Entra settings stop someone (for example Assignment required), they see a Microsoft error page, not the sota request page.
- The client secret expires. The secret you create in Entra is valid for at most 24 months. Create a new one before it expires, or sign-in stops working.
Risks we accept for now
- Cookies from other sota apps. Your apps live under
sota.io, next to apps of other sota customers. A browser lets any site undersota.ioset cookies for the whole domain, so another customer's app could plant a cookie that your app then receives. The sota Access session itself is protected against this (it uses a host-only__Host-cookie). If your app uses its own cookies for anything important, treat their content as untrusted input. Your own domains, coming next, remove this risk. - Apps on your server can reach each other. Your apps share your server's container network and can call each other directly, without the sign-in. This stays inside your company; apps of other customers run on other servers.
- Sign-in depends on the sota platform. If the sota API is down, people who are already signed in keep working until their session ends, but new sign-ins wait, and a block you set during the outage takes effect when the API is back.