Who controls the system?
You set the objective, standing permissions, authorised channels and budget. Material changes require the appropriate approval. App agents cannot rewrite their own spending restrictions or mandatory release safeguards.
What security work is included?
The agreed scope covers dependency monitoring, code and configuration checks, testing suitable patches, tracking unresolved risks and escalation. Your portal will show findings and remediation evidence when the operating integrations are connected.
Where does data go?
This pilot uses Supabase for authentication and application records in EU West (Ireland). The website is hosted on Fly.io in Amsterdam. For a customer app, we confirm model providers, subprocessors and retention arrangements before launch.
What do you own?
Ownership and access to application-specific code, data, domains and accounts are defined in your agreement, subject to third-party licences. Our reusable service platform remains separate from your application.
AVAILABLE NOWA place to begin.
Public pilot enquiries, email and passkey accounts, and an invited test workspace for briefs, review feedback and recorded approvals. Each customer can access their own records and assigned projects.
NOT YET IN THIS PILOT WORKSPACEConnected operation.
Live monitoring, provider billing, security findings and separate pause controls for development, marketing and the live app are not connected. The sample dashboard illustrates the planned experience.