SECURITY · DEPLOYMENT FACTS

Written for the person
doing the security review

Send your architecture team this page. It answers what they are going to ask anyway, in the order they usually ask it, and it says plainly where our answer is we do not claim that.

The short version

The control is the deployment model, not a certificate

Studio runs on hardware you own, inside a boundary you already defend. Your firewall rules are the enforcement. Nothing here depends on trusting a promise we made in a questionnaire.

Where does it run?
A Docker Compose stack on infrastructure you own: VPC, private data center, or an isolated network. Images can be mirrored into your own registry.
What talks to the outside?
In a self-hosted deployment, nothing in the install path requires a call to us. Inference defaults to a local endpoint, and payment processors are disabled entirely.
Where does the AI run?
Against your model server: Ollama or vLLM on your GPUs. If you choose to permit egress, you can point it at a commercial API with your own key instead.
How does licensing work?
A signed licence key validated offline against a signature on your machine. There is no licence server, no activation call, and no usage metering.
Who can log in?
Your directory. LDAP / Active Directory / OIDC single sign-on, with local accounts optional and self-registration disableable.
What about our data at rest?
Your PostgreSQL and your object storage, on your infrastructure, under your encryption, backup, and retention policy.
Can it run air-gapped?
Yes. Offline install from mirrored images, a local model server, and an offline licence. We will do the install with your team on a machine with no route to the internet.
What telemetry do you collect?
From a self-hosted deployment, none. There is no usage reporting, no crash upload, and no analytics beacon in the product. This website has Google Analytics; the product you run does not.
Verify it yourself

The configuration is the evidence

You do not have to take the paragraph above on trust. This is the real on-premise configuration, and your team can read every line of it before anything runs.

application-onprem.properties
# the real config. no hidden endpoints.
deployment.mode=onprem

# inference points at your box, not ours
OPENAI_BASE_URL=http://localhost:11434/v1  # ollama

# no billing calls, no licence server
razorpay.enabled=false
paddle.enabled=false

# your directory, your mail, your storage
LDAP_ENABLED=true
MAIL_HOST=smtp.internal

What we do not claim

We do not hold SOC 2, ISO 27001, or HIPAA attestation, and we will not tell you otherwise to get through a procurement gate. We are a small company in Hyderabad. When we have an audit, it will be on this page with the report date.

We also do not publish an uptime SLA for self-hosted deployments, because we do not run them. Availability is your infrastructure. What we do commit to in the licence is a named support engineer and an agreed response time.

If your process requires a certified vendor, we are the wrong supplier today and we would rather say so now than in month four of a procurement cycle. If your process cares about where the data physically sits and who can reach it, keep reading, because that is the part we are built for.

Next step

Bring your security team to the call

We will walk your architecture and security reviewers through the compose file, the licence mechanism, and the network boundary, and answer the questions this page did not. Bring the questionnaire if you have one.

Book a deployment call Email the team