Deployment & hosting

The default: Raytio operates the platform, and you consume it as a service with the entitlements your plan grants.

The entire platform deploys into your own AWS account.

• Data never leaves infrastructure you control.
• Encryption keys are held in your account's key management service.
• Your security team keeps its own audit and monitoring.

Every resource - network, database, identity pools, storage, queues, permissions - is declared in code and provisioned by it. Nothing is hand-built in a console, so environments are reproducible and reviewable.

The network foundation (VPC, subnets, security groups) deploys first, then the platform layer on top. Remote state is versioned and locked, so infrastructure changes are as controlled as code changes.

Development, staging and production are built from the same definitions, differing only in parameters. Parameters are held in a parameter store, with secrets encrypted.

The platform runs on functions, managed queues, object storage and a managed PostgreSQL database. There is no server fleet to patch, and capacity follows load.

Database migrations and function deployments run as ordered, repeatable steps - the same path every environment takes, including ours.

We plan to operate an EU zone with all infrastructure and data staying within the EU, for customers with European data residency requirements. Self-hosting already achieves residency today: deploy into an EU region of your own AWS account.

The managed service is multi-tenant with database-level isolation; self-hosting gives you a dedicated stack.