Authorization boundaries
Agent deploy uses one-time pairing sessions; uploads are allowed only after the user confirms the project in the browser. Trusted device credentials can be revoked anytime in the console.
How PocketBay handles build isolation, container permissions, environment variables, access logs, user authorization, legal entity, and support channels.
The following describes high-level controls currently implemented. They are not absolute security guarantees and do not replace your responsibility for your own code and dependencies.
Agent deploy uses one-time pairing sessions; uploads are allowed only after the user confirms the project in the browser. Trusted device credentials can be revoked anytime in the console.
All build sources share concurrency, memory, and time limits, with isolated networking to reduce impact on the host and other apps.
User containers use dedicated networks, block direct container-to-container communication, limit PIDs, and drop all Linux capabilities by default before restoring minimal permissions.
Public-prefix env vars may enter frontend builds; other secrets are injected at runtime only, avoiding write into image build layers.
User-controlled content such as logs and errors is marked untrusted so platform Copilot does not treat app output as system instructions.
The platform records builds, deploy status, and gateway metrics; public app traffic has paths and sensitive query params redacted, and plaintext IP is not used as a product analytics field.
Do not access other users' data, disrupt production services, or disclose unfixed details publicly. Send reproducible steps, impact scope, and suggested fixes to the support email.
Submit security report →