Inkling

Meet Inky

Just say what you want.

Inky reads your site — the pages, the shapes they take, your images, your menus, your categories, your settings, even which social networks you have half-connected — then does the thing you asked for. It shows you the change before anything is saved, and when the last step is one only you can take, it puts you on the right screen.

→ you
Add a page about our new roastery, and put it in the menu

→ inky
read your page shapes … 3 kinds
read two existing pages, for the voice
drafted "Our Roastery" — intro, body, hours
queued a menu item under Visit

Both are waiting for you to look at. Nothing is live yet.

→ you
I want to start posting these to Instagram

→ inky
read your social setup … no app registered for Instagram
opened Social → Settings

Instagram goes through a Facebook app, which is the part
that catches everyone out. I'll walk you through it — are you
an admin of the Page the account is linked to?

What it holds

Shape the content, not the page.

You describe what a product, a post, or a landing page is made of. Inkling gives your team the screens to fill it in, and your sites one clean way to read it back.

Models

Your own shapes

Repeating sections, image galleries, links between records. No field type you have to work around.

History

A real edit history

Every save keeps what it replaced. Read an old version before you restore it, and undo the undo.

Sharing

Show work early

Send an unpublished piece to anyone with a link that opens for an hour and expires on its own.

Together

Move together

See who else is in a record while you're in it. Nobody edits a version that changed ten minutes ago.

Timing

Publish on a schedule

Set the hour and step away. Anything that no longer fits its model comes back to review rather than going out broken.

Access

Roles that hold

Writers keep to their drafts, editors publish, admins shape the model. Change a role and it takes effect on the next click.

What your sites read

One request, whole page.

Ask for a piece of content and the images and linked records come back filled in — not as references you have to go and fetch. Drafts never appear here, whoever asks.

→ the site asks for one product

{
  "slug": "blue-lotus",
  "title": "Blue Lotus Refresher",
  "publishedAt": "2026-07-30T09:12:04Z",
  "data": {
    "price": 7.5,
    "image": {
      "url": "…/blue-lotus.jpg",
      "alt": "A tall glass, condensation",
      "width": 1600
    }
  }
}

While you work

The change arrives on its own.

When something goes live, your sites are told. No timer polling for news, no cache you have to guess the age of.

Live updates: Your sites hear the moment a piece is published, pulled, or replaced. They're told what changed, then read it back the way they always do.
In the room: Names appear on a record while your colleagues have it open. Nobody discovers the collision at save time.
Ask for anything: Inky is in the corner of every screen, and knows what you're looking at. "Reword this", "add a section for quotes", "take the promo off the menu" — it proposes, you approve, and it lands in your history under your name.
Answers for visitors: Add a chat bubble to your public site with one line. It answers from what you've published, follows the rules you write, and says so plainly when the answer isn't there.
Your model, your money: Bring Claude, OpenAI, or Ollama — local or hosted. Nothing is on until you connect one, and you can turn it off again.
Many at once: Select a season's worth of posts and publish, archive, or retire them together. Each is checked on its own, and you're told which didn't pass.
Extendable: Add your own sections, screens, and content shapes as self-contained pieces. Switch one on and it's there — nothing restarts, nothing rebuilds.

Where to go

Pick up the reel.

Twenty minutes from an empty database to a site reading live content.

Start →

Roll it.

Run it, open the admin, start writing. The first person through the door becomes the owner.

Get started → Source