Security
Multi-tenant isolation, layer by layer
Robots act in the physical world, so the systems serving their policies must keep tenants apart. These are the controls vlaport is designed around.
Credentials per company project
Every company project gets its own credentials. Access to one project's endpoints does not open another project's.
Authentication at the edge
Endpoint requests carry a JWT issued by vlaport's identity provider. The gateway validates it before a request reaches your model.
EU hosting
Endpoints are designed to run only in an EU GPU region, hosted in EU data centres.
Your weights, your data
You bring your own policy weights. Data recorded for your robots belongs to you and can be exported in LeRobot format (planned).
Approval and quota for GPUs
GPU deployments stay pending until they are approved and given a quota.
No tokens in the browser
The web app at app.vlaport.com uses a server-side session. Creating API tokens requires step-up authentication, and no tokens are kept in the browser.
Security in how we build
No secrets live in the repository, and CI will scan for secrets on every change. Every change goes through a pull request with an independent review against security and tenant-isolation rules, and isolation will be checked by automated tests before release.
Status
vlaport is in development. This page describes the design, not a certification or an audit. A threat model and security hardening are part of the plan before release.
Become an early-access design partner
vlaport is in development. We are looking for robot-learning teams who serve openpi or LeRobot policies today and want to shape a managed, EU-hosted endpoint with us. Tell us about your robots and policies.
Sign-up is by email only. This site has no forms, sets no cookies and collects no personal data.