SECURITY
We work inside your perimeter.
That's a responsibility we designed for.
Most vendor security pages describe how they protect your data on their systems. Ours is simpler: your data never reaches our systems. What follows is how we keep it that way while building inside your network, and after we hand it off.
- 1Your data never transits our systems
- 2Access you grant, scope, and revoke
- 3Nothing phones home
- 4Restricted networks are a practiced motion
- 5Pinned, verifiable, reproducible
- 6Evidence your review process can use
DATA LOCALITY
Your data never transits our systems
Models, prompts, outputs, documents, and logs live on your storage, inside your network or your cloud accounts. We do not host inference, we do not proxy traffic, and we are not a processor in your data path. There is nothing of yours on our side to breach.
ACCESS MODEL
Access you grant, scope, and revoke
Access runs through your identity provider under named individual accounts. No shared credentials, no standing back doors. You set the scopes, you see the session logs, and revocation is a switch you own. Access flows through your VPN, bastion, or PAM tooling, per your policy.
NO TELEMETRY
Nothing phones home
The platforms we build send no usage data, metrics, or crash reports to Deplero or anyone else. Monitoring runs on your infrastructure and alerts your team through channels you choose. We hold no pager into your environment. Air-gapped sites are handled the same way, via your approved transfer process.
AIR-GAP
Restricted networks are a practiced motion
Fully disconnected environments are supported end to end: signed artifact bundles delivered through your controlled transfer process, installed and upgraded without any outbound connectivity. Deplero was founded by an engineer who shipped air-gapped installers at hyperscale.
SUPPLY CHAIN
Pinned, verifiable, reproducible
Every component we deploy is version-pinned and pulled from sources you can inspect: upstream open-source projects and your own registries. Image digests are recorded in your infrastructure-as-code, so what runs in production is provably what was reviewed. SBOMs available on request.
AUDITABILITY
Evidence your review process can use
Deployments include structured logging of platform events (model loads, configuration changes, access grants) retained on your storage under your retention policy. We map controls to your internal security framework and sit with your reviewers when asked.
Standing commitments
Written into every engagement. Not negotiated per deal.
These terms are written into our agreement because a security posture you have to negotiate for isn't a posture. It's a discount. If your review process needs evidence for any of them, ask, and you'll get an answer straight from engineering.
IN THE STANDARD AGREEMENT
- No customer workloads on Deplero-owned or Deplero-rented hardware, structurally, not as policy
- No shared credentials; every action we take is attributable to a named individual
- No outbound telemetry from anything we build
- All infrastructure-as-code and runbooks live in your repositories
- Access revocable by you, unilaterally, at any time. Access degrades gracefully, not catastrophically
- Security questionnaires answered directly by Deplero engineering, not a sales desk
Working with your compliance program
Your framework. Your auditors. Our evidence.
We don't claim certifications we don't hold, and we won't name-drop frameworks as marketing. What we do: design deployments to satisfy the controls your compliance program actually requires (data locality, access control, logging, change management) and produce the documentation and evidence your internal and external reviewers ask for. Architecture reviews with your security team are part of every assessment, not an add-on.
Put your security team on the call.
Seriously, bring them to the first conversation. The engagements that go best are the ones where security asks the hard questions in week zero.
Book a demo