PloyDB

The databasebuilt intoyour website.

Store structured content in Ploy, edit it like a spreadsheet, and let your site, forms, automations, and Ploy’s Agent work from the same source.

One source, every surface

Your content stops living in five different places.

Tables give recurring content one consistent shape. Your team edits the records, Ploy understands the structure, and every connected experience stays current.

Illustrative PloyDB workspace

Blog posts

4 records · Live updates

Search records
TitleStatusAuthorUpdated
Introducing PloyDBPublishedBryantToday
The joy of a living websitePublishedElianaYesterday
Why AI search changes contentIn reviewEmmaAug 4
A practical guide to AEODraftBryantAug 2

  • Live site

    Index and post pages

  • Ploy’s Agent

    Draft, edit, publish

  • Forms

    New rows as they arrive

  • PloyBooks

    Automate the workflow

No separate database account, vendor, or integration layer to manage.

More than a CMS

If it repeats in a consistent shape, put it in PloyDB.

CMS is the easiest place to start. The same foundation also powers listings, catalogs, submissions, and structured application data.

  • CMS

    Blogs, changelogs, and case studies.

    One template renders every record. Add a row, publish it, and the index, detail page, tags, metadata, and structured data stay consistent.

    See the CMS & blogging setup

  • Directories

    Jobs, teams, customers, and events.

    Turn repeatable records into filterable lists and individual pages that update from the same table.

  • Catalogs

    Products, plans, and feature libraries.

    Keep names, descriptions, pricing, status, and supporting details structured instead of scattered across pages.

  • Forms

    Requests, waitlists, and RSVPs.

    Write new submissions into a table with scoped write access, then let your team and automations work from the incoming records.

PloyDB can also hold accounts, users, sessions, and other application records when your project needs a real data layer beyond website content.

How it works

Describe the data. Ploy connects the rest.

Start with a sentence, a CSV, or an empty table. Ploy's Agent can propose the structure, build the pages that use it, and create the scoped access your published site needs.

  • Describe

    Tell Ploy what you are keeping track of.

    Ask for a blog, jobs board, customer directory, event calendar, or a custom data model. Ploy proposes the tables, columns, and field types before anything is created.

    • Start from plain language, an existing CSV, or an empty database
    • Use typed fields for text, numbers, dates, status, people, URLs, and more
    • Create as many tables and databases as your workspace needs

  • Connect

    Turn rows into pages and submissions into records.

    Ploy builds the templates, list views, detail routes, filters, forms, and access keys that connect your site to the data.

    • One page template can render every published record
    • Read-only keys power public content; write-only keys protect form workflows
    • Ploy stores access keys as site secrets after your approval
    Read the database docs

  • Operate

    Keep the site current from one shared grid.

    Edit cells, add records, change statuses, or ask Ploy to make the update. Connected pages read the latest published data without rebuilding the entire site for every change.

    • Filter, sort, reorder, and edit records in real time
    • Use draft, review, scheduled, or published states that fit your workflow
    • Restore a checkpoint or any moment from the rolling 30-day history
Built for live data

Fast to change. Hard to expose by accident.

Ploy handles the connection between your published site and its data without turning every page into an all-access client.

  • Scoped access

    Every key belongs to one database. Grant read, write, both, or neither for each table, and keep public-page access separate from form submissions.

  • Secret columns

    Sensitive columns are hidden from Ploy’s Agent. Credential-like fields are protected automatically, and a person controls whether a secret can be revealed.

  • Reversible changes

    Use named restore points or rewind the database to any moment in the rolling 30-day history. Every restore creates an undo point first.

Who it’s for

For every team keeping the site current.

Marketing teams

Publish without turning every content change into a project.

Run blogs, changelogs, case studies, landing-page libraries, and directories

Keep recurring content consistent with shared fields and templates

Update records directly or ask Ploy to do it in plain language

Keep every generated page inside the site’s design system

Content teams

Manage the editorial workflow in a grid everyone understands.

Use custom statuses for draft, review, scheduled, and published content

Edit titles, dates, authors, tags, and cover images without code

Keep required fields consistent across every entry

Publish one new record without rebuilding every existing page

Builders & operators

Connect structured site and application data without maintaining another tool.

Model products, events, accounts, users, sessions, and internal records

Import CSVs and query or bulk-load data through the Ploy CLI

Scope read and write permissions table by table

Hide sensitive values from Ploy’s Agent with secret columns

PloyDB FAQ

Website databases and CMS, answered.

PloyDB is the structured-data layer built into Ploy. It stores content and records in databases made of tables, typed columns, and rows. Your website, forms, automations, team, and Ploy’s Agent can work from that shared source.
No. PloyDB is built into Ploy, so you can create tables and connect them to your site without signing up for a separate database or CMS platform. There is no external database account, vendor contract, or integration layer to manage.
A CMS is one core use case for PloyDB, but not the only one. You can use it for blogs, changelogs, case studies, jobs, directories, product catalogs, form submissions, or application records. PloyDB provides the data layer; Ploy builds the website experience around it.
No. Describe what you want to model and Ploy can propose the schema, create the tables, import a CSV, build the connected pages, and configure the access keys after you approve the changes. You can also manage the database visually.
Content and record edits on connected pages normally appear on their own, usually within a minute, without republishing the site. Changes to site code, templates, or newly added secrets still follow the normal publishing workflow.
Yes. A site can use a scoped write-only access key for forms and other collection workflows, while separate read-only access can power public pages. Permissions are configured by table, and new keys start with no table access.
Access keys are scoped to one database and configured table by table for read, write, both, or neither. Secret columns are hidden from Ploy’s Agent, and columns that look like credentials are hidden automatically. Databases also keep a rolling 30-day history with restore points.

Give your site one source of truth.

Create a database, describe the pages it should power, and let Ploy connect the structure, design, and publishing workflow.

Or book a demo