Skip to content

The data belongs with the application

Lahyer Databases.

Give your application a managed Postgres database. Keep the connection beside your code and environment settings, with room for your first real users.

Add Postgres
PostgreSQLEXAMPLE PROJECT / STOREFRONT
Database example view

A place for your app's data.

Managed Postgres. A connection string. Your choice of database client.

Engine
PostgreSQL
Included on Free
1 database / 1 GB
Connection
Project-specific credentials
Application setting
DATABASE_URL
Your app connects with its own credentials.Choose a project
1 database1 GB included on Free
10 databases10 GB each on Pro
PostgresUse the libraries you already know

Keep the setup together

From connection string
to useful data.

Use PostgreSQL with your application code. Bring your preferred client, ORM, and migrations.

Create it inside a project.

Choose a project and open its Database tab. Plan allowances are shared across your organization, so you can see what is available before creating another database.

Connect with project-specific credentials.

Use the connection string from your project. Store it as a server-side environment variable instead of committing it to Git or exposing it in browser code.

Use your own application stack.

Connect with a PostgreSQL client or ORM such as Drizzle or Prisma. Your schema and migration workflow remain part of your codebase.

Three organized data towers with stacked records and connection lights form a managed database district.

A considered default

One application.
One clear connection.

Keep credentials private, run migrations deliberately, and track your storage allowance as the application grows.

Explore the developer workflow

A few useful answers

Before you begin.

Are database limits per project or organization?

The database count is per organization. Free includes 1 database up to 1 GB. Pro includes 10 databases, each up to 10 GB.

Does Lahyer migrate my application schema?

Your application owns its schema and migrations. Use your existing migration tools and test changes before applying them to production data.

Can a frontend connect directly?

Do not expose a Postgres connection string in browser code. Put database access behind server-side code with your application's authentication and authorization rules.