Protect your workspace

Project files and AI output are treated as untrusted. The application does not execute generated code or offer a shell on its server.

Account boundaries

Private projects use server-side ownership checks. Administrative routes require an administrator role, and sensitive admin changes are audited. New accounts never receive administrator access automatically.

Payments and credits

Stripe webhooks use signature validation. Event processing and credit allocation share database transactions. Credit spending locks the user's balance row to prevent double spending.

Private files

Marketplace archives use private application storage. Downloads require ownership and a short-lived signed route. Malware scanning is required before publication. Scanner errors do not allow approval.

Safe development

Do not store real secrets in project files. Path restrictions help prevent unsafe archives but cannot detect every embedded credential. Review generated code, dependencies, and redistribution rights yourself.