How it works

Describe it. Watch it build. Ship it.

Forge takes a brief to a working SmartLinks app, with the platform connected and the infrastructure handled from the start.

A workspace for each app

Open an app and it gets its own workspace: the conversation on the left, the real running app on the right. Nothing to install, no environment to set up — the machine that builds your app starts the moment you open it.

You can switch the right-hand side from the live app to the code at any time, edit a file directly, and watch the preview update.

Build the experience. SmartLinks runs the machinery.

There is no database to provision, sign-in system to assemble, server to maintain or deployment pipeline to wire together. Your app starts on the secure identity, data, hosting and services already provided by SmartLinks.

Forge can still build server-side workflows and connect to outside systems. Their credentials stay sealed away from the app, and SmartLinks runs the resulting work for you.

An agent that already knows the platform

The agent starts every app with the SmartLinks platform already understood: identities for physical things, who owns them, the data attached to them, the permanent record of what happened, sign-in, forms, messaging, loyalty, analytics, numbering, and the built-in AI toolset.

That means it leads with a solution rather than reading its way around. It won't rebuild something the platform already provides, and it won't invent a capability that doesn't exist.

Need another system in the loop? It can write server-side code that talks to your ERP, CRM or anything else with an API, with the credentials held in a sealed store rather than in the app.

Real context, not placeholders

Choose one of your own collections and item types, and the preview runs against the real thing. What you see is what a customer or an operator will see.

Test every view

An app doesn't live in one place. Forge lets you load each view the way it actually runs — including the operator setup screen inside the genuine signed-in SmartLinks console, so sign-in, navigation and theming behave exactly as they will in production.

History you can undo, publishing without ceremony

Every change is saved automatically as you go, so you can look back through what happened and restore any earlier point — no version-control knowledge required.

When you're happy, send a test version to a real SmartLinks account, check it in context, and publish the finished app without assembling your own release process.

The views an app can have

App panel

The app's main panel inside a SmartLinks page.

Who sees it
The public — someone who tapped a tag, followed a link, or is browsing Hub.
Where it appears
Inside SmartLinks Portal and Hub pages, alongside the other apps on that item.

Small card

A compact tile that summarises the app with a way in.

Who sees it
The same public audience, browsing rather than arriving.
Where it appears
Side menus, link pages and hub cards, next to other apps' cards.

Full public page

The app's own full screen, not embedded in anything.

Who sees it
The public, a display screen, or anyone following a shared link.
Where it appears
Anywhere on the open web — a phone, a laptop, a wall-mounted display.

Setup screen

Where the brand turns the app on and configures it.

Who sees it
The operator running the brand — not the public.
Where it appears
The SmartLinks console, in the app's settings area.

On-the-go screen

A handheld operator screen inside SmartLinks Sidekick.

Who sees it
Staff on their feet — a warehouse, a venue, a site visit, a delivery round.
Where it appears
The SmartLinks Sidekick mobile app, which is where operational work happens.

Machine-readable content

What search engines and AI assistants are told about the page.

Who sees it
Google, and the AI assistants people now ask instead.
Where it appears
In the page's own head and in the crawler-readable content Hub serves.

Ready to make one?

Pick an idea