Real environments, properly fenced.
Students get real cloud accounts and real machines. That only works if every environment is isolated, short-lived and cleaned up — and if your data is handled with the same care.
Lab isolation
Every cloud lab runs in its own AWS account from a managed pool, scoped by organisation policy to the services that lab is about. Container labs run in per-student sandboxes. Sessions are time-boxed and everything created in them is removed at the end; accounts are verified clean before they are reused.
Your data
We store what we need to run your account, your progress and your certificates. Authentication is handled by Supabase Auth with Google and GitHub sign-in; passwords, when used, are never visible to us. Payments are processed by Razorpay, Dodo Payments and Stripe — card details never touch our servers.
Colleges
Each partner college runs on its own subdomain with its own roster and data boundary. Faculty and administrators see only their institution. Lab reports, outcome data and placement analytics are exportable by the college and owned by the college.
Built on AWS Well-Architected
The platform follows the AWS Well-Architected security pillar: least-privilege IAM, service control policies at the organisation level, encryption at rest and in transit, centralised logging, and automated remediation for drift in lab accounts.
Responsible disclosure
Found something? Read the responsible disclosure policy and write to security@deployu.ai. We respond quickly and we don't pursue good-faith researchers.