# A database of your own

Last checked 16 October 2026.

The same page on the web: https://dev.fline.sh/docs/database

This page helps you give your app a place to remember things, like sign-ups, bookings or messages. It explains what fline creates when you ask, how your app finds its database, who can reach it, how to pause or delete it, and how to use a database you already have instead.

## Ask Claude Code for one

If your app needs to remember things between visits, ask Claude Code. It reads your project and tells fline what kind your app needs.

```prompt
My app needs a database. Have fline create one for it.
```

You may not need to ask. When fline reads your project to put it online, it looks for a database your app uses, and Claude Code tells you if anything is needed from you.

## What fline creates

fline can create a Postgres database for your app and run it for you. If your app needs a fast cache instead, fline creates one with Valkey, which is Redis-compatible.

- **One small size.** Each database gets 1 GB of memory and room for about 8 GB of data. There's no bigger size yet.
- **It belongs to your account,** not to one project. It stays when you change your app or delete a project, and more than one of your projects can use it.
- **You can see it** on the Services page of [your fline dashboard](https://app.dev.fline.sh). You can also create one there yourself.

## How your app finds its database

Your app has to be told where its database is: one line that holds the database's address and its password. Claude Code takes care of that with fline.

If it needs you, Claude Code asks you to copy that line from your fline dashboard and tells you where it goes. When you paste it, use fline's private page or your dashboard, not the chat. See [Passwords and keys your app uses](https://dev.fline.sh/docs/keys).

## Who can reach it

Your database is on the internet, so your app can reach it. It's locked with a password and encryption: it takes only encrypted connections, and only with its password.

You can also limit who can reach it. Open the database on the Services page of your dashboard and add the addresses you want to allow under "Who may reach it".

## Pause it, or delete it

You can pause a database and resume it later. While it's paused, nothing can reach it, including your app, and its data stays where it is.

If you delete a database, its data is kept for seven days, then destroyed. After the seventh day nothing can bring it back. Claude Code should ask you before it deletes one.

```prompt
Pause the database my app on fline uses. I'll ask you to resume it later.
```

## Keep your own copy

Keep your own copy of anything you can't lose.

We don't promise backups yet, there's no way to restore, and there's no button to download your database. Putting an earlier version of your app back doesn't change what's in your database.

## If the database password gets out

Your fline dashboard can give the database a new password. The old one stops working, with no overlap, so your app can't reach the database until it has the new line too. Ask Claude Code to help you put the new line in place before you do it.

## Use a database you already have

Already have a database (Postgres, MySQL, MongoDB, Redis or RabbitMQ)? Connect that instead. Claude Code tells fline what kind it is, and you type its address on fline's private page, the same page you use for keys.

```prompt
My app should use the database I already have, not a new one. Set that up on fline and give me the private page for its address.
```

Next: [Use a web address you own](https://dev.fline.sh/docs/web-address) or [Change your app after it is online](https://dev.fline.sh/docs/update-your-app)