Ploy's agentic CMS (PloyDB) explained: what it stores, who needs it and where it stops

By Ranjit Bhinge, founder of Blur Studio · Updated · 9 min read

Short answer: PloyDB is the built-in database inside Ploy, an AI website and marketing platform. You edit it like a spreadsheet, and Ploy's AI agent builds one page template that turns every row into its own page. That makes it a content management system (CMS, the place where you keep and edit blog posts, listings and similar content). Ploy calls it an agentic CMS because an AI agent can set it up and edit it for you. Limits include 97 columns per table, 128 KB per text value and a CSV (spreadsheet file) export cap of 10,000 rows.

Ranjit Bhinge

You keep hearing that Ploy has an agentic CMS and you want to know what it stores, whether you need it and what the limits are before you move content into it.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

PloyDB is a spreadsheet-style database that powers pages on your Ploy site. Each kind of content gets a table, each item is a row, and each property is a column. One template can then turn all of the rows into pages. As of November 2026, Ploy's docs say that publishing a post or a listing can be as simple as adding a record, and that edits usually reach visitors within a minute, without a republish.

Ploy is an AI platform from Ploy, Inc. that builds and edits websites through a chat with its agent. This guide explains PloyDB in plain words, what the label "agentic CMS" means, what it stores, who needs it, how to move content in, and where it limits you. For the bigger idea, read what an agentic CMS is.

This page may contain affiliate links from which Blur Studio earns commissions.

What "agentic CMS" means

There is no standard definition. Vendors use the phrase in two ways. Optimizely, a content and marketing software company, describes an agentic CMS as a content management system enhanced with autonomous AI agents. Uniform, another software company, describes one that serves both people and AI agents. In Ploy's case, the useful reading is this: you manage content by chatting with an AI agent, and outside AI tools can also reach your content through Ploy's MCP server (MCP is a standard way for an AI app to use another tool). Treat the label as marketing, and judge the product by what it does. See how Ploy's MCP connection works for the outside-tool side.

What PloyDB stores

Ploy's docs say to use a database whenever content repeats in a consistent shape. The rule of thumb on its page: if you would keep it in a spreadsheet, it belongs in a database. The docs list these uses:

  • Blog and changelog posts, such as announcements and release notes.
  • Listings and directories: jobs, team members, customers, events.
  • Catalogs: products, pricing tiers, features.
  • Form submissions: contact requests, waitlist sign-ups, event RSVPs.
  • App data: accounts, users, sessions and similar records.

For one-off content, such as a homepage hero or an About page, just edit the page. Column types include text, number, currency, percent, checkbox, single and multi select, status, people, date, URL, email, file and relation (a link to a row in another table). Files are private to your workspace, up to 10 MB each, in JPG, PNG, WebP, SVG, PDF or plain-text types. Visitor uploads cannot supply images that your site displays. Those go in the Assets library.

How rows become pages

  1. You describe what you want, for example "a /jobs page listing every open role by department, with a detail page for each".
  2. Ploy's agent proposes tables and columns and creates them once you approve.
  3. It builds one list page and one detail template connected to the table.
  4. From then on, adding or editing a row changes the live page. Per the docs, edits usually reach visitors within a minute.

The site reads the table with an access key, a credential that is limited to chosen tables. New keys have no table access until you set it. A common setup is a read-only key for pages that show content and a write-only key for forms. The key is shown once, so copy it when you create it. Ploy's agent normally creates and stores the key for pages it builds.

For a blog, Ploy's docs recommend backing it with a database. The blog includes an index page, post pages, tag pages, and per-post titles, descriptions, share images and structured data. Existing long-form content is moved in verbatim and not rewritten. Always review before publishing.

Who needs it, and who does not

Use a database if:

  • You have 20 or more items of the same type, such as team members, locations, jobs, case studies or products.
  • Non-technical people must edit content without touching the page design.
  • You want form submissions saved in a table you can filter, not only emailed.
  • You plan to publish many pages from structured facts that really differ from row to row.

Skip it if:

  • You have a five-page brochure site. Just edit the pages.
  • Your content has no repeated shape. A database adds work with no gain.
  • You need an editorial workflow with roles, approvals and scheduled publishing across many writers. Ploy's docs describe owner, admin and member roles, but not an approval or scheduling workflow for writers. Check whether that fits your review process before you commit.
  • Your site stays on another host. PloyDB powers Ploy-hosted pages. You can read it from your own app through its API, but that is a developer job.

A warning about pages made from rows

A database makes it easy to publish hundreds of pages. That is a risk as well as a strength. Google's spam policies define scaled content abuse as many pages generated mainly to manipulate search rankings and not to help users, "no matter how it's created". Doorway abuse covers pages made to rank for similar searches that funnel people to one place. Ploy's docs do not discuss search rankings for database pages. Clay, a sales data company, is named on Ploy's blog as a programmatic SEO (publishing many search pages from data) customer, but that is a vendor claim, not proof of results.

Use this test before you publish a row-based set of pages:

  1. Would this page exist if search engines did not? If not, do not publish it.
  2. Does each row carry facts that are different and useful, such as real prices, real photos, real service areas or real reviews you hold?
  3. Can a person who lands on one page get a full answer there?
  4. Has a person read a sample of at least 10 pages, from the thinnest row to the richest?
  5. Are weak pages kept out of search with a noindex tag (a code that tells search engines to skip a page), or not published at all?

A made-up example. A plumber with 12 service areas could put the areas in a table with columns for local rules, typical response time, real job photos and a local phone number. If four of the 12 areas have no real jobs or facts yet, publish eight and hold four. A city name swapped into the same text is the pattern Google warns about. Read doorway pages and thin content at scale and whether Google penalizes AI-written pages before you scale.

Moving content in from another CMS

You can paste a content URL into chat and ask Ploy to analyze the old CMS. Per Ploy's CMS migration doc (last updated November 13, 2026), nothing is written during the analysis. You then review the collections, fields and record counts, choose what to import, and decide on a new or existing database. Supported sources and what to expect:

SourceHow it connectsNotes from Ploy's docs
WordPress (a widely used site builder and blogging system)Public content URL, no connection stepPosts, pages, custom post types
Squarespace (a hosted website builder)Public content URLBlog, store and portfolio collections
Sanity (a headless CMS, meaning a content tool without its own site front end)Public datasets by URL, or a connected tokenDirect project import possible
Webflow (a visual website builder)One-time secure connectionCMS collections and typed fields
Framer (a visual website builder)One-time secure connection with project URL and API keyCMS collections and typed fields
Wix (a hosted website builder)One-time secure connectionUser-built collections only; Stores, Bookings and Coupons are skipped
Notion (a note and database app)One-time secure connectionShared databases become tables; relation and rollup properties are skipped

Important cautions from the same page: owner or admin access is needed, a re-import is not a sync (it creates fresh tables and does not remove duplicates), a cell that cannot be read is left empty and the import is marked partial, and complex or proprietary embeds may have no direct equivalent. Spot-check media-heavy content after the import. For the wider move, see Ploy site migration, and keep your old URLs working, because Ploy's docs say to add 301 redirects (permanent forwards from an old address to a new one) for any address that changes.

Limits, cost and exit

  • Size limits: up to 97 columns per table, 128 KB per text value, CSV imports up to 32 MB, files 10 MB each. Writes from published sites are rate-limited to protect the database.
  • Export: you can export a table view as CSV, up to 10,000 rows. If more rows match, the download is cut off and the dashboard warns you. Ploy's own page says CSV is for interchange, not backup. Options export as labels, list values use semicolons, and files export only as names.
  • Backup: Ploy keeps a rolling 30-day history of every database. Only owners and admins can restore, and you can make a named restore point before a risky change.
  • Developer access: a backend, serverless function or mobile app can read and write through an API (a way for software to talk to software). Ploy's docs say not to call it from browser JavaScript, and to keep the key as a server-side secret.
  • Secret columns: columns that look like credentials are hidden from the agent automatically. You can mark any column as secret.
  • Cost: there is no separate database fee on Ploy's pricing page. Agent work, such as building tables, tagging many rows or rewriting posts, uses AI credits. Check Ploy pricing, and check whether Databases is switched on in your workspace.
  • Lock-in: Ploy's FAQ says you can download your site's source code on every plan. Your table data is a separate matter: a 10,000-row CSV cap and "not a backup" wording mean you should plan your exit before you load thousands of rows. Use the API or the PloyDB command line tool for a full copy. See who owns your website and content.
  • Data terms: Ploy's terms say you keep your content and that Ploy does not use customer data to train its AI models on any plan. The terms say export is available for 30 days after termination, while the privacy page says 60 days. Treat 30 as your deadline.

A 20-minute export test before you commit

  1. Create a table with 50 sample rows and one file column.
  2. Export the table view as CSV. Open it. Check that dates, select options and list values look right.
  3. Re-import the CSV into a new table. Check what changed, especially the file names.
  4. Clone the site source with Ploy's command line tool and look at how the pages read the table.
  5. Ask a developer if they could rebuild the pages on another host with the CSV and the code.

Pass: you can rebuild from what you exported. Fail: you depend on something that only exists inside Ploy. Then keep a second copy in a spreadsheet or your own database.

How I'd approach this

Do not move your whole site into a new CMS first. Pick one table, one page type and one owner.

  1. Day 1. List your repeating content (posts, locations, team, jobs). Choose the one with the most edits per month.
  2. Day 2. Open a Ploy workspace and ask the agent for a table for that content, with the columns you already use. Approve the plan only after reading the column list.
  3. Day 3. Import 20 to 50 real rows, from a CSV or from your old CMS. Spot-check every field type.
  4. Day 4. Generate the list and detail pages. Review the pages on a phone. Fix wording by hand.
  5. Day 5. Run the export test above, and set an access key with the smallest rights it needs.
  6. Day 6. Have the person who will edit the content make three changes in the grid, without help. If that is easy, the CMS is doing its job.
  7. Day 7. Decide using the pass and fail lines: edits live within minutes, pages are useful on their own, export works, credits are affordable.

Pick PloyDB if your site is on Ploy or moving there, your content repeats in a clear shape, and non-technical people edit it. Skip it if your site stays elsewhere or if you have a handful of pages. If you want a custom content system, where AI agents use your business knowledge and connect to your CRM and calendar, Blur Studio builds the custom version, and you can see what that includes. To try the database side first, you can start on Ploy's free plan and test one table.

The scheduled workflows that read and write this data are covered in PloyBooks explained.

Related guide: programmatic and service-area landing pages for local clients.

Related guide: sales pages for distributors and manufacturers.

You may also want manufacturer and distributor product and spec pages.

Questions people ask

What is PloyDB?

PloyDB is Ploy's built-in database that you edit like a spreadsheet. Tables hold rows of content, and Ploy's AI agent builds page templates that turn each row into a page. It works as a CMS for blogs, listings, catalogs and form submissions.

Is Ploy's agentic CMS a standard product category?

No. "Agentic CMS" is a vendor term with more than one meaning. Some vendors mean a CMS with AI agents built in, others a CMS that AI agents can operate. Judge Ploy by its features, not by the label. See what an agentic CMS is.

How many rows or columns can PloyDB hold?

Ploy's docs list up to 97 columns per table, 128 KB per text value, CSV imports up to 32 MB and files up to 10 MB. They do not state a row limit on that docs page, so ask Ploy support before you load a very large table.

Can I export my PloyDB data?

You can export a table view as CSV, up to 10,000 rows, and Ploy says CSV is for interchange, not backup. It also has a 30-day rolling history and a command line tool and API for fuller access. Test the export before you rely on it.

Can I move my WordPress or Webflow blog into PloyDB?

Yes, per Ploy's CMS migration doc. WordPress uses a public content URL. Webflow needs a one-time secure connection. A re-import is not a sync, so use a clean database each time. See Ploy site migration.

Will database-generated pages rank on Google?

No tool can promise that. Google's spam policies cover scaled content made mainly to manipulate rankings. Pages need real, different facts and a person's review. See doorway pages and thin content.

Who can edit PloyDB content?

Workspace members with access to the database can use its grid. Owners and admins manage access keys and restore versions. Free plans cannot invite collaborators, so check the plan page first.

Does PloyDB cost extra?

Ploy's pricing page lists no separate database fee. Work done by the AI agent, such as building tables or rewriting many rows, uses AI credits. See Ploy pricing explained.

More in this topic: Ploy.ai: the product, pricing and reviews (12 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…