Resources
Managed databases, caches, storage and queues StrictOps runs for you
Resources
Most apps need more than just the code that runs them — they need somewhere to store data, somewhere to keep things fast, somewhere to put files, and a way to do slow work in the background. Those are resources.
StrictOps provisions and runs each resource for you inside your own AWS account, keeps it patched and backed up, and connects it to your services automatically. You don't manage servers, connection strings, or credentials by hand.
What you can add
| Resource | What it's for | Injected as |
|---|---|---|
| PostgreSQL | Your app's core data — users, orders, posts | DATABASE_URL |
| Redis | A fast cache for sessions and speeding up reads | REDIS_URL |
| S3 Bucket | File and object storage — uploads, images, exports | S3_BUCKET |
| Queue (SQS) | Background jobs so slow work doesn't block requests | QUEUE_URL |
How linking works
When you add a resource, you link it to the services that need it. For each linked service, StrictOps injects a connection string as an environment variable (the one in the table above) at deploy time.
- Credentials are generated and rotated by StrictOps — they're never written into your repository.
- A service only sees the resources you link to it.
- You can link one resource to several services (for example, an API and a worker that share the same database).
Cost
Each resource shows an estimated monthly cost on its card, based on the plan and size you pick. You can change the plan later; pricing scales with the size you choose. See each resource's page for guidance on picking a starting size.