Websites
Server-rendered pages on their own address or your domain, read properly by search engines, AI crawlers and link previews.
One app, many surfaces, all sharing the same data.
Server-rendered pages on their own address or your domain, read properly by search engines, AI crawlers and link previews.
The mobile experience a scan or tap opens, with navigation and sign-in. Apps appear inside it as panels.
Small cards (small, medium, large, with display options) and full app components that other pages embed and that follow their theme.
Full-screen public views for TVs, kiosks and live leaderboards.
Each app's admin screen inside SmartLinks Studio, plus cards on the business's dashboard: "3 new enquiries".
Sidekick screens for phones and handheld scanners, with camera, QR, NFC and RFID, and offline queues.
A semantic theme system (including AI-generated themes) and translations across every surface.
Customers, members and staff are already modelled. No login to build.
Email and password, magic links, phone codes, Google and WhatsApp. A site can have its own login, with its own users.
One record per person, created when they sign in, register or fill in a form, with custom fields. Searchable, shared across your collections.
A members' area is contacts with a level (gold, junior, pending). No separate membership system to run.
Claim an item by NFC tap, serial number or code; transfer it to a new owner; share access with others.
Admin access checked by the platform, with two-step verification by authenticator app.
Public, owner and admin tiers on data, with personal fields kept in their own boundary.
A content system the business edits itself, which any site or app can show.
Posts, FAQs, team members, events, anything: queryable records with statuses and visibility, attachable to a product or item.
Apps declare their content (FAQ, blog, gallery, pages) so any website can render it, while it's still edited in the app's admin.
Images, video, audio and documents with permanent addresses: replace a picture once and every page updates. Large resumable uploads and web-ready video.
Product and item fields with declared schemas, variants, batches, facets and tags.
A Liquid template library for messages and documents.
Useful objects with rules built in, not an empty database.
Any app-specific entity: registrations, inspections, entries, results.
Work moving to a resolution, with assignment, priority, status and history.
Conversations and Q&A tied to a person, product or item.
Append-only, hash-chained facts (an inspection, a service, a verification), with public, owner and admin tiers.
Slots, bookings and allocations for tickets, classes, appointments and hire, with atomic multi-part bookings and availability.
Managed form definitions and submissions, with schema-driven screens.
Collections, products, variants, batches, lots and individual items, each with its own data and history.
Nested groupings (case, pallet, shipment) with history; atomic numbering and one-per-person claims.
Know what people do, and reward it.
Typed events (scans, votes, entries, registrations) with outcomes. They feed analytics, journeys and loyalty.
React to what people do, and build audiences from behaviour and contact fields.
Schemes and earning rules: points are awarded automatically when an interaction happens. Balances, lifetime points and history.
Page views, clicks and QR and NFC scans, with dashboards.
Screens update the moment data changes; live channels for votes, boards and presence.
Every channel, with consent built in.
Email, SMS, WhatsApp, push and wallet passes, or each contact's preferred channel.
Transactional sends from an app, a server function or an event.
Multi-channel broadcasts with preview and test sends.
A booking confirmation or an enquiry alert, with reply-to, cc and bcc, and attachments: calendar invites, files, generated documents.
Topics, opt-ins and opt-outs, preferences and unsubscribe handling.
The physical world as a way in, and a way to work.
A QR code or NFC tap opens exactly the right experience for exactly that item.
NFC read and write, including NTAG 424 DNA tags for authenticity; tag ranges for manufacturers and partners.
On supported Android handhelds (built-in, Zebra and TSL readers): mass-scan a shelf or pallet, filter by EPC, and find a tag with a Geiger-counter mode.
Stock counts, goods in and out, inspections, servicing and ticket scanning, recorded against each item.
Real back-end code, without a server to run.
App code the platform runs: on a web request (public or admin), on a platform event, on a schedule, or as an agent tool.
Credentials for outside services are stored write-only and never reach the browser.
Call any API, from a fixed address that partners can allow-list.
Third-party code can run in an isolated runner, scoped to what it declares.
Functions have test and live versions, released with the app.
AI as a platform service, with no keys in the browser.
Platform chat, plus assistants grounded in the business's own content and manuals.
Web search and page reading, document reading, typed data extraction, image generation and editing, PDF creation and form filling, translation.
Speech to text, text to speech and podcast-style audio.
Apps can expose their own actions to the SmartLinks agent.
Alongside the systems you already run, not instead of them.
Apps that know one outside system (a PIM, a content network, a shop platform), installed and versioned like any app.
Send data out with deterministic field mappings, on demand or when something changes. Failed records retry on their own. Inbound and scheduled flows are next.
Server functions receive calls from other systems and verify the caller.
Forge writes the extraction for any source (an old site, a CMS export, a spreadsheet, an API) and loads it into the cloud.
Published, delivered and versioned for you.
Apps and sites on a global network, with server rendering at the edge.
An automatic address, a chosen name or your own domain, with certificates handled.
Immutable, versioned builds through test, beta and live channels. Each business chooses its version; major upgrades are opt-in.
See every surface against a real business's data while you build: the portal, cards, admin and mobile screens.
Guard rails as building blocks.
Admin writes and visibility tiers are enforced by the platform, not the app.
When the assistant acts for an admin, sending, deleting, publishing and spending wait for an "Allow", and changes can be undone.
Consent and scoped data are building blocks; your own data handling and legal duties still need review.
Start with a website, an app for your products or a tool for your team.
Start building