Private deployment
Run the model gateway inside your network. Prompts and outputs stay in your perimeter, and upstream keys never leave your infrastructure.
Enterprise
Run the studio inside your perimeter
For teams with compliance, residency or key-management requirements, StaroleStudio can run with a private gateway, your identity provider and local models.
Talk to usSSO and roles
Connect your identity provider, map groups to roles, and keep administrative actions behind your existing access policies.
Audit and retention
Every administrative action is recorded. Set retention windows that match your internal policy and export them for review.
Data residency
Choose where account and usage data live, and keep local models for workloads that cannot leave the building.
How a pilot works
Step 1
Scope
A 45-minute call to map your deployment target, identity provider and the workloads you want to bring in.
Step 2
Pilot
We deploy a private gateway and two or three workflows with a small group, usually within two weeks.
Step 3
Rollout
Once the pilot is signed off, we hand over runbooks, admin training and a support channel.
What we ask before a pilot
- Your deployment target: cloud account, on-premises, or a single workstation.
- The identity provider you use, and who will administer roles.
- Two or three real workflows, so the pilot measures something that matters.
- Your security questionnaire, if you have one. We fill it in before the first call.
Enterprise features are being built with design partners. Tell us what your team needs.
support@starole.com