cd /news/ai-agents/your-app-is-the-memory-the-model-is-… · home topics ai-agents article
[ARTICLE · art-138794] src=oncroft.net ↗ pub= topic=ai-agents verified=true sentiment=· neutral

Your app is the memory. The model is not.

Croft launched a platform that gives every app a real SQLite database on a private server, arguing that durable facts such as rosters, stocktakes and signed quotes belong in an app's database rather than in a model's chat context. In a September 6, 2026 blog post, founder Rich Chetwynd outlined three rules — write durable facts into the app, read from the app on the next turn, and let people see, fix and delete their data — and said shared data on the same croft lets apps read each other's records without duplicating state in a prompt. Croft costs from $24/month with a 7-day free trial and no card required.

by read2 min views1 publishedSep 5, 2026
Your app is the memory. The model is not.
Image: source

Blog · September 6, 2026 · Rich Chetwynd A nut allergy, a default store, last week's roster: those facts belong in your app's database, not in a chat transcript. Croft gives every app a real store.

An assistant that “remembers you” is only as good as where it writes that down. If the fact lives in the model’s context, it dies with the session, leaks into the wrong prompt, or cannot be deleted when someone asks you to forget it.

For a shopper, that might be a shoe size. For a business it is the roster, the stocktake, the open quotes. Those are not memories. They are records. They belong in a database you own.

Store it where you already work #

Every app on Croft gets a real SQLite database on your private server. The assistant can create tables, write rows, and query them. The roster is in the roster app, not in last Tuesday’s Claude chat.

That is also how you share state across apps: shared data on the same croft, with access you grant on purpose. The quotes app can read customers without a second copy of the truth living in a prompt.

The model should not be the system of record #

Three practical rules, the same ones you would use for any client:

  • Write durable facts into the app. A new hire, a received delivery, a signed quote. If you would be angry to lose it, it is not chat history.
  • Read from the app on the next turn. Do not ask the person to re-type yesterday. Open the list.
  • Let people see, fix, and delete it. A database you can export is a database you can honour a deletion request on. A transcript is not.

Connectors fit the same split. Stripe, a CRM, email: the platform holds the key, the app reads and writes through it, the model never becomes a second copy of billing.

What this gives you #

You can change assistants. Build in Cursor this month, Claude next month. The app is still there, the rows are still there, the login is still yours. Your data is yours.

The model is how you change the tool. The app is how the tool remembers.

Stake out your croft. #

Your team's first app could be live before lunch.

Get your croft 7 days free, no card to start. From $24/month - cancel anytime and take everything with you.

── more in #ai-agents 4 stories · sorted by recency
── more on @croft 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
Live at https://your-agent.zahid.host
Get free account → Pricing
from €0/mo · no card required
LIVE [news/your-app-is-the-memo…] indexed:0 read:2min 2026-09-05 ·