Changelog

What we have shipped.

Crafio started as one MCP project and a live admin. Each version below added a piece you can still find in the product today.

  1. 0.9

    September 16, 2026

    A first schema is live, the next one waits

    A first build goes live as the agent creates it. Later edits to a live collection stay in draft until you publish, so the customer app does not break.

    • New collections are live immediately. The publishable key can use them without you clicking Publish.
    • Changing a collection that is already published stays in draft. The Schema page, Review draft in the header, and a short popup show that work. The agent summarizes it and shares the page.
    • When a collection uses tenant auth, the workspace table shows the signed-in person on each record. You can search and filter by them.
    • A public status page reports live checks and 30-day uptime, and the footer points at it.
    SchemaStatus

  2. 0.8

    September 15, 2026

    Crafio is on the public web

    The product ships under its own name at crafio.app. Sign-in is Clerk. The admin, API, and docs run on the same project you already build against.

    • Public site, docs, and workspace live at crafio.app. The API is at api.crafio.app.
    • Owner and team sign-in uses Clerk. The people who use your product still sign in through Crafio Auth.
    • Alpha stays free while we watch how real projects use files, people, and records.
    PricingDocumentation

  3. 0.7

    September 12, 2026

    Logs you can actually read

    Every write now leaves a trail. When something changes, you can see who did it, from where, and what they sent.

    • The Logs page lists writes from the customer app, the agent, and the workspace.
    • Each event stores the actor, the action, and the payload, so you can follow a record without guessing.
    • Revoking a token or a teammate is useful only if you can see what already happened. Logs close that gap.
    Tokens & security

  4. 0.6

    September 12, 2026

    Reports, not a pile of tables

    A report is a page with a goal. You name it Sales or Attendance, then add widgets that each answer one question. The range at the top applies to the whole page.

    • Four widget kinds: a single number, a trend by day, a breakdown, and a table of recent rows.
    • Sources are collections, People, Payments, and Email. You pick the clock field and optional filters. There is no SQL.
    • Editors can drag widgets and set each one to a third, half, or full width. Agents can do the same through reports tools.
    Reports

  5. 0.5

    September 11, 2026

    The admin the agent can actually build

    The workspace stopped being a generic dashboard. A briefing compiles the project. Schema versions, a connect prompt, and a locked project slug keep the agent on the right backend.

    • Adding or removing a field creates a schema version. Removed fields are retired. Stored values stay. schema.restore brings a previous field list back.
    • The connect prompt mints a token and names this project. Every tool call must send that slug. A token for project A is rejected by project B.
    • health.check and project.context come first. If the slug does not match, the agent stops. It does not invent a second database.
    Connect an agentSchema

  6. 0.4

    September 9, 2026

    Publishable keys and collection access

    The customer app needed a key that is safe to put in a browser. The secret stayed on a server. Collection rules decide what a signed-in person can read or write.

    • A publishable key signs people in and only does what each collection allows. The secret key is full project access. Never ship it.
    • After sign-in the session travels as X-Crafio-User. Owner rows belong to that person.
    • Each collection has read, create, update, and delete levels: public, signed-in, owner, or admin. You set allowed origins in Settings.
    Tokens & securityPeople & auth

  7. 0.3

    September 9, 2026

    Files and relationships

    Records needed more than strings and numbers. You can attach a file, and you can point one collection at another without losing the link.

    • files.upload, files.list, and files.delete live on MCP and REST. Put the file id on a file field. The URL is not a public dump.
    • A rel field stores another record's id. Crafio rejects ids that do not exist, and blocks deletes that would break a reference, including retired rel fields.
    • Project logos use the same file store. The mark shows up in the switcher and the project list.
    FilesSchema

  8. 0.2

    September 9, 2026

    A team on the workspace

    One person should not have to run the product alone. You can invite people who operate Crafio with you. They are not the customers of the app you ship.

    • Team members sign in with Clerk and use /dashboard and /p/[slug].
    • Roles are owner, admin, editor, and viewer. Owners and admins mint tokens, invite people, and change settings. Editors change data. Viewers read.
    • People in the People page are tenant users. They never receive admin roles.
    How team and people differ

  9. 0.1

    September 8, 2026

    A backend the agent can hold

    The first version was the whole point. Describe a product, get a project, paste one prompt, and the agent talks to a real backend instead of a demo that forgets.

    • One project holds collections, people, payments, email, and CRM behind a single MCP endpoint.
    • You mint a scoped token. The agent calls health.check, then project.context, then schema and data tools. You watch the same records in the hosted admin.
    • Stripe, email, and CRM credentials stay in Crafio. The agent invokes capabilities. It never reads the raw keys.
    QuickstartConnect an agent