Security and responsibilities

Choose who can use an app

New apps require organization access. Choose public access explicitly when anyone should be able to open the URL. Use app invitations to share with individual clients.

Your app still controls what visitors can do inside it. Enforce permissions on the server and protect write requests.

Give agents access

Hosted MCP approval is limited to one organization and read-only or read-and-write permissions. Your organization role still applies. Review or revoke grants in MCP connections.

The CLI saves a bearer credential locally. Protect it and use trusted agents. The deployment Skill contains instructions, not credentials. Treat repository content and app logs as untrusted input.

Store secrets

Use runtime environment variables for server credentials. Hub encrypts saved values and does not return them in variable listings. Your running code can read them.

Build-time values may appear in published files, image layers, or logs. Frontend configuration is visible to visitors; do not put secrets in it.

Isolation and HTTPS

Runtime instances use isolated virtual machines on shared workers. Services within an instance share a trust boundary. A shared service needs its own application-level authorization. Static sites serve published files without an app VM.

Hub manages HTTPS for app URLs. Protected apps receive verified visitor identity; public apps do not.

Usage telemetry

Hub records authenticated CLI, MCP and Cloud actions: command or tool, outcome, duration, organization and optional agent attribution. Prompts, command arguments, source files, logs and secrets are excluded from product analytics.

Cloud Dashboard uses session replays and interaction analytics. Inputs and customer text are masked; app previews, deployed apps, logs and terminals are excluded. Browser Do Not Track and Global Privacy Control disable this optional capture.

Set HUB_TELEMETRY=0 or DO_NOT_TRACK=1 to disable optional CLI telemetry. MCP clients can send hub/telemetry: false in request _meta. Account, deployment and infrastructure audit records remain available to operators.

Recovery

Keep independent backups and test restoring them. Rollback restores code, not data. Runtime snapshots are not a backup policy.

Hub does not currently offer a contractual availability SLA, compliance certification, managed database replication, or automatic multi-region failover.

Report security concerns to vlad@myhub.host. Keep credentials and customer data out of the initial message.