PostgreSQL
Managed relational database, provisioned in seconds with credentials auto-injected.
Appentic provides managed PostgreSQL with automatic daily backups, point-in-time recovery, and connection credentials injected directly into every service in the same project. The database isn't something you bolt on as an afterthought: from a developer's perspective, provisioning a database and using it in code is a two-minute operation.
Creating a database
From your project dashboard, click New resource, then PostgreSQL. Pick a tier, pick a region (usually the same region as the services that will read from it), and click Create. Provisioning takes about 30 seconds, after which the database is ready to accept connections.
Each database has a generated name, a random strong password, and a postgres:// connection string. None of that is something you have to manage.
Connecting from a service
Because the database lives inside a project, every service in that project automatically receives a set of injected environment variables:
DATABASE_URLis the full connection string, ready to pass to your ORM or driver.PGHOST,PGPORT,PGUSER,PGPASSWORD,PGDATABASEare the individual components if you need them separately.
Use whichever style your driver prefers. In Node.js with Prisma you'd set DATABASE_URL in your schema and be done; in Go with lib/pq you'd parse the same URL; in a Python app with SQLAlchemy you'd pass it straight to create_engine. You don't copy credentials, and you don't redeploy when a credential rotates: the injection picks up the new value automatically.
Backups
Daily backups are taken automatically and retained according to your workspace plan. From Database → Backups, you can restore any backup to a new database (the original is never overwritten), which makes recovery drills a low-risk thing you can actually run.
Resizing
You can resize a database up (more CPU, more RAM, larger disk) with no downtime from Database → Settings → Machine. Scaling down requires manual verification that your new size has enough storage for the current data, because shrinking disk with active data in it is the kind of thing you want a human involved for.
Connecting from outside Appentic
If you need to run a one-off migration, a seed script, or a psql session from your laptop, the dashboard exposes a temporary psql command you can copy and paste. The credentials work for a limited time window, so you don't end up with permanent DB creds in your shell history.