Resources
Managed databases and key-value stores attached to your services.
A resource is a managed piece of infrastructure that your services depend on but don't directly run. In practice, this means the data layer of your application: databases and caches.
Appentic supports two kinds of resource today:
- PostgreSQL. A managed relational database. Provisioned with a single click, backed up automatically, resizable without downtime, and accessible via the standard
postgres://connection string. - Key-value store. A Redis-compatible in-memory store for caches, rate limiters, session storage, and lightweight pub/sub. Any Redis client library works without modification because it speaks the same wire protocol.
How resources connect to services
When you create a resource inside a project, its connection credentials are automatically injected into every service in the same project as environment variables. A PostgreSQL database provides DATABASE_URL (plus the individual PG* components), and a key-value store provides REDIS_URL (plus REDIS_HOST, REDIS_PORT, REDIS_PASSWORD).
You don't copy connection strings around, you don't store them in a secrets manager, and you don't have to redeploy when a credential rotates. The service just reads process.env.DATABASE_URL (or the equivalent in your language) and it works.
Lifecycle
Resources live inside a project and are deleted when the project is deleted. You can also detach a resource from a project if you want to keep the data but reorganise where it lives. Deleting a resource is permanent: snapshots are retained only as long as your workspace's backup policy allows.