Your agent,briefed on your data.
Add your prices, hours and policies once. Visitors get answers from them in seconds.
Your visitors ask. Your tables answer.
“How much is delivery to 78704?”
$9.95, and it arrives the next day.
Bring your data in. Type it, import it, describe it, or send it.
Start from nothing. Name it, pick the columns, and type your rows in.
Bring a spreadsheet. Drop a CSV or JSON file, and the columns and their types are found for you.
Describe it, or drop in files. AI builds the table and fills it, from a sentence, a PDF or a photo.
Straight from your AI tools. They create tables and add rows over MCP, into the same place.
Asked in their words. Found in your tables.
The way people talk. No keywords, no menus to learn.
Ten rows or ten thousand. The right one surfaces.
Nothing is searched until you allow it. Checked again with every question.
Every answer can lead somewhere. Tappable next questions, built in.
Powered by Postgres.
Tell the Data agent. Or edit by hand.
Every table starts hidden from the chat. Share the ones that should answer.
Every connection is encrypted. From your dashboard to the database.
Visitors only ever read. No visitor can edit a single row.
Spotted when you share a table. Listed for you to review first.
You choose what agents can change. Safe from the start.
Frequently asked questions.
Only the ones you switch on. Each table has its own switch and your site has one too, both off at the start, and they're checked on every question. Turn a table off and the next answer leaves it out.
No. Visitors only read. The chat looks things up and never changes a row.
When you switch a table on, any columns that look personal, like an email or phone column, are listed before you say yes.
CSV and JSON files import straight into a table, with the columns set up for you. Create with AI also reads PDFs and photos, and the Data agent takes CSV, JSON, text, Markdown and PDF files.
Only as far as you allow. Agents start on Safe: they can add and edit rows, but never delete a whole table. You can turn them off or allow Full, and Confirm destructive asks once more before a table, a column or many rows go.
In a Postgres database. Every row belongs to its site, and the database only ever hands a site its own rows.