--- title: "A Database for Your Website, Built In | Briks" url: https://briks.dev/features/database description: "Sites that store data get their own database. View and edit the records in the studio, and on a paid plan download them as JSON or CSV and keep nightly copies." last_updated: 2026-10-08 --- On every plan # Your records, in your own database Menus, listings, bookings and team members belong in a database, not in your page's text. Sites that store data get their own, and you can see and edit every record from the studio, and download them all on a paid plan. ## How it works 1. **Built with your site** When your site stores data, its database comes with the build. 2. **Edit in the studio** Open the Database tab to view and change records. 3. **Download on a paid plan** A collection as CSV, or everything as JSON. ## What goes in the database Some things on a website change often and come in lists: the breads on a menu, the rooms in a guest house, the projects in a portfolio, the people on a team. When a site keeps things like these, Briks gives it a database of its own and stores them there as records, grouped in collections, rather than writing them into the page's text. That keeps everyday edits small. In the Database tab you can search a collection, open a record, change a price or a description, and save it. Records can be kept as drafts, which stay off the published site until you are ready. Owners and Admins can also create a database by hand from the Database tab, for a site that did not need one when it was built. A site with sign-in for its visitors keeps their accounts there too, and a site that takes payments its orders and subscriptions. The Database tab shows each in its own view: Accounts, Orders and Subscriptions. ## Taking your records with you Your records are yours to take. On a paid plan, download everything as one zip, with each collection as JSON and a description of how it is made up, or download a single collection as a CSV spreadsheet with a column for each field. Exports hold up to 50,000 records per collection; if a collection has more, a note in the zip says so. Every change can also tell another tool. Add a webhook for the record changed event, and each record added, changed or deleted is sent to the address you give. Where a database is kept is set when it is made, and its records never leave that place. ## Going back in time The database keeps its own history. Owners and Admins can take it back to any minute within that history, in their own time zone, or to a restore point you named. Save one before a big change, such as "Before the spring menu", and it is easy to find again. For a longer safety net on a paid plan, switch on nightly copies: a copy of the whole database every night, kept for 30 days and downloadable from Backups. They count towards your plan's storage and are off until you switch them on. The actions you cannot take back are kept apart, in a danger zone: clearing a collection, and deleting the database, which asks you to type the project's name first. ## When a site needs a database If a part of your site is a list that changes, it belongs in the database: menus, rooms, classes, products, team members, case studies. If it is a paragraph that rarely changes, such as your story on the About page, it can stay as words on the page and be changed in plain words. Records make small changes quick. Changing a price in the Database tab edits one record; it does not start a build. ## Your own database in practice Three example businesses, and how each would use it. Where a site is pictured, it is a sample Briks built for an example business, not a customer. 1. Bakery **This week's bread** A bakery keeps its breads in a collection: a name, a price and whether each is on sale. On Friday the owner opens the Database tab, switches the cardamom bun off sale and changes the price of the rye. [![The opening of Sourdough, a sample site Briks built for an example bakery and coffee shop](https://briks.dev/showcase/sourdough.webp)](https://sourdough.briks.live/) **Sourdough** is a sample site Briks built for an example bakery and coffee shop, not a customer. [Open the sample](https://sourdough.briks.live/) 2. Bed and breakfast **Rooms as records** A B&B's rooms are records with a name, a description and a nightly price. Before raising prices for the summer, the owner saves a restore point called Before summer prices, so the old prices are one restore away if she changes her mind. [![The opening of Hollyhock House, a sample site Briks built for an example bed and breakfast](https://briks.dev/showcase/bed-and-breakfast.webp)](https://bed-and-breakfast.briks.live/) **Hollyhock House** is a sample site Briks built for an example bed and breakfast, not a customer. [Open the sample](https://bed-and-breakfast.briks.live/) 3. Web design studio **Case studies kept as drafts** A web design studio keeps its case studies as records, each with a slug, and keeps new ones as drafts until the client signs off. Once a quarter it downloads the collection as CSV for its own archive. [![The opening of Northlight Studio, a sample site Briks built for an example web design studio](https://briks.dev/showcase/website-studio.webp)](https://website-studio.briks.live/) **Northlight Studio** is a sample site Briks built for an example web design studio, not a customer. [Open the sample](https://website-studio.briks.live/) ## What you get - A database of its own for each site that stores data - View, search and edit records in the Database tab - Download as JSON or CSV on paid plans, up to 50,000 records per collection - Go back to any minute in its history, or to a named restore point - Owners and admins can also create one by hand ## Questions about your own database ### Does every site get a database? Sites that store data do. An owner or admin can also add one from the Database tab. ### Can I back it up? Yes. Save restore points on any plan. On a paid plan, download your records at any time and switch on nightly copies. ### Can I go back to yesterday's records? Owners and Admins can take the database back to any minute within its history, or to a named restore point. Nightly copies, on paid plans when switched on, are kept for 30 days. ### How much can I export? On a paid plan, up to 50,000 records per collection, as CSV for one collection or as JSON for everything. ### Which plans can download records? Every paid plan. On Free you can view, edit and restore your records, and downloads and nightly copies come with a paid plan. ### Can I search my records? Yes. Each collection can be searched in the Database tab. ## Related features - [Paid plans **Nightly database copies** On a paid plan, switch on nightly copies and Briks copies your site's database every night and keeps each copy for 30 days, so you can go back after a mistake. How it works](https://briks.dev/features/nightly-copies) - [On every plan **Forms that keep every entry** Forms on your Briks site keep every entry in the studio and, once the site is in production, email each one to you. No form service to connect. How it works](https://briks.dev/features/forms) - [On every plan **Your site's code** Briks shows the code written for your site. Browse the files, edit them by hand if you like, and on a paid plan download a version as a zip from the studio. How it works](https://briks.dev/features/your-code) [See all 32 features](https://briks.dev/features) ## Try it on your own business Describe it in a sentence and Briks builds it. Start free with the credits you get at sign-up.