Who Enterprise tier is for
If your organisation has one of these requirements, Enterprise is the right fit:
- On-prem mandate — source code must not leave the perimeter.
- Air-gap setup — no outbound internet, possibly local LLM via proxy.
- Multiple users — architecture team, shared projects, run history traceable per person.
- Container-mandatory sandbox — every agent in isolated container.
- SLA — contractual response time, escalation path, hotfix contract.
- Audit demands — beyond built-in audit log, e.g. SIEM integration.
Three Enterprise deployment variants
Enterprise customers choose between three deployment models. The technical license is the same Ed25519-signed JWT in all cases; the difference is in operations, lease duration and network requirements.
Enterprise Cloud
SaaS in our tenant. You get a dedicated tenant on license.softwarefabrik.io. 30-day lease with automatic renewal.
Right fit when:
- You do not want to operate the license server infrastructure yourself
- EU hosting at Hetzner / Falkenstein is acceptable
- Devices and users may refresh against the public
license.softwarefabrik.io
Enterprise Self-Hosted
We ship the Docker Compose setup. The license server runs in your data centre. Licenses reference the internal URL; clients refresh exclusively there. 90-day lease.
Right fit when:
- Data sovereignty is a contractual or regulatory requirement
- Development environments live in isolated networks
- You have operations teams familiar with Docker / Kubernetes
Enterprise Air-Gap
Offline certificate valid for 365 days, renewed annually via USB stick or controlled file transfer. No network connection.
Right fit when:
- Your network is strictly isolated (public authorities, defense, critical infrastructure)
- On-prem LLM operation is feasible (e.g. Ollama, vLLM)
- Annual renewal can be handled organisationally
Enterprise building blocks
Delivery
- Self-hosted Docker bundle — signed images, own license-service setup in the same network.
- Air-gap bundle — all dependencies as offline tarball, including Postgres image, Java distribution, container base image.
- Optional own branding: logo, colours, footer notices.
Multi-user
- Multiple user accounts with roles (USER, ADMIN).
- Per-user workspaces; shared projects with ACL.
- Audit log with user attribution per action.
- Tenant status: tenant foundations (project-boundary isolation, RBAC, SSO) are in place; full audit-grade multi-tenancy (separate policy/audit/reports per tenant) is still to come — until then, one instance per tenant is recommended. Details under Known Limitations.
SLA
- 4h email/ticket response.
- Hotfix delivery on agreement.
- Monthly status call for roadmap alignment.
- Pre-configured backup and DR runbooks for the self-hosted stack.
Air-gap in detail
Air-gap setups are their own league — they always have organisation-specific constraints. We deliver:
- Tarball with all container images as
docker saveformat. - License service as local setup — no internet license check, lease issued by on-prem license service.
- Local LLM provider proxy (on request) — if an internal LLM endpoint (e.g. self-hosted LLama or Azure OpenAI in own tenant) is to be used. Platform adapters speak standard OpenAI or Anthropic format.
- Update mechanism via signed bundle — updates come as tarball with Ed25519 signature, applied manually.
Example customer profiles
- Mid-sized company with 50 developers, SaaS-friendly: Enterprise Cloud. 30-day lease, SSO via OIDC, audit log, priority support.
- Financial services company with data sovereignty requirements: Enterprise Self-Hosted. License server in own data centre, 90-day lease, data stays in-house.
- Public authority or defense supplier: Enterprise Air-Gap. No network, 365-day lease, on-prem LLM (e.g. Qwen 3 Coder / DeepSeek V3.2).
How an Enterprise engagement starts
- First conversation — constraints, compliance, in-house stack, pilot scope.
- Pilot phase (4–8 weeks) — self-hosted, one team, one workload. Goal: quality-gate verdict for a real use case.
- Roll-out phase — further teams, multi-user setup, on-prem license service.
- SLA contract — with pre-configured response time, backup and DR agreements.
Inquiry form
We get back to you within two business days. The form sends to enterprise@softwarefabrik.io. Currently only email delivery is active; the backend for order processing will come online at the public launch.
What happens next?
- Confirmation email to you within minutes
- Call-back or email reply from an account manager within two business days
- If interested: NDA, discovery call, followed by an individual offer