SYS.INT's Enterprise tier adds a dedicated cluster, a named SLA, and an on-prem or air-gapped deployment option on top of everything in the Pro tier.
It adds a dedicated compute cluster or an on-premises install, SSO and RBAC identity controls, and a 99.99% uptime SLA backed by service credits. Dedicated deployments start provisioning in 2 to 4 weeks; a full On-Prem install takes 6 to 12 weeks depending on your network review.
What does the Enterprise tier add on top of Pro?
Five controls ship with every Enterprise contract: a documented security posture, a named uptime SLA, a choice of on-prem or air-gapped deployment, a dedicated compute cluster, and SSO/RBAC identity integration. Each is available at contract signature, not as a later add-on.
Security posture
Every request is authenticated, scoped to a role, and written to an append-only audit log with actor, resource, and timestamp attached.
Named SLA
99.99% uptime, written into the contract with service credits attached. P1 incidents get a first response inside 15 minutes, 24 hours a day.
On-prem and air-gapped
Run the full inference stack on hardware you own, with zero outbound network calls. Model weights and request logs stay inside your facility.
Dedicated compute
A cluster reserved for one contract, not a shared pool. No latency spikes from other tenants running on the same nodes.
SSO and RBAC
SAML and OIDC single sign-on, with role-based permissions scoped down to individual models and edge regions.
Which deployment option fits your infrastructure?
SYS.INT ships in three shapes: a shared Cloud pool, a Dedicated single-tenant cluster, or a fully air-gapped On-Prem install. The table below compares compute isolation, data residency, provisioning time, and support across all three.
| Spec | Cloud | Dedicated | On-Prem |
|---|---|---|---|
| Compute | Shared multi-tenant pool | Isolated cluster, single tenant | Customer-owned hardware |
| Data residency | Provider-selected region | Region pinned in contract | Stays inside customer facility |
| Network path | Public internet, TLS 1.3 | Private VPC peering available | Fully air-gapped, no outbound calls |
| Provisioning time | Immediate | 2-4 weeks | 6-12 weeks |
| Support channel | Standard ticket queue | Dedicated Slack channel + on-call | On-site engineering available |
| Uptime SLA | Best-effort | 99.99%, contracted | 99.99%, contracted |
What security and compliance controls does SYS.INT document?
The Enterprise tier documents encryption, role-based access, audit logging, and incident response for every contract, with controls mapped to SOC 2 and ISO 27001 practice areas. SYS.INT is template demo content and holds no real compliance certification.
Template placeholder. The controls below describe this fictional demo product's sample security posture, shown to illustrate how a compliance section can read. No SOC 2, ISO 27001, or HIPAA certification is claimed or held for this product. Replace this section with real audit evidence and your own certification marks before adapting this template for an actual company.
| Spec | Implementation |
|---|---|
| Encryption | TLS 1.3 in transit, AES-256 at rest |
| Access control | Role-based permissions, scoped per resource |
| Audit logging | Every request logged with actor, resource, and timestamp |
| Incident response | Documented runbook, notification window set in contract |
| Data residency | Region pinning available on Dedicated and On-Prem tiers |
| Framework alignment | Mapped to SOC 2 and ISO 27001 practice areas, not certified |
Enterprise deployment questions, answered
Straight answers to what operations and security teams ask before signing an Enterprise contract.
01What SLA does the Enterprise tier include?
The Enterprise tier ships with a 99.99% uptime SLA written into the contract, backed by service credits if it is missed. P1 incidents get a first response inside 15 minutes, 24 hours a day, 7 days a week.
02Can we run this fully air-gapped, with no outbound network access?
Yes. The On-Prem deployment option installs the full inference stack on hardware inside your facility with zero outbound network calls. Model weights and request logs never leave the building.
03What is the difference between Dedicated and On-Prem?
Dedicated reserves an isolated compute cluster inside SYS.INT's own cloud for your contract alone. On-Prem installs the same stack on hardware you own and operate, for teams that cannot send data outside their own network.
04How does SSO and RBAC provisioning work?
Enterprise accounts connect through SAML or OIDC single sign-on. Roles are scoped down to individual models and edge regions, so a support engineer and a platform admin see different slices of the same account.
05How long does an Enterprise deployment take?
A Dedicated cluster typically provisions in 2 to 4 weeks. A full On-Prem install takes 6 to 12 weeks, depending on your network review and hardware procurement timeline.
06Is SYS.INT SOC 2 or ISO 27001 certified?
No. SYS.INT is fictional demo content built for this template and holds no real compliance certification. Its documented controls (encryption, role-based access, audit logging) are written to align with SOC 2 and ISO 27001 practice areas, shown here as sample content for how a compliance section can read.
Ready to talk to sales?
Tell us whether you need Cloud, Dedicated, or On-Prem, and we will scope the SLA, the timeline, and the security review with you before you sign anything.
Talk to Sales