What you skip
The foundations for serious apps, already here
Identity and sign-in
Customer and operator accounts, ownership and permissions are already there.
Per-item data
Every unit has its own record, history and custom fields. You don't design a schema to get started.
Hosting and delivery
Publishing puts the app on a global delivery network. There are no servers to size or patch.
Background jobs
Scheduled and event-driven server functions run on the platform, scoped to the right permissions.
Secrets
Keys for outside services stay sealed server-side and never ship in the app.
Integration plumbing
Connect to the systems you already run through server functions and platform integrations.
Security is part of the architecture
A stronger starting point than a blank project.
Identity, permission-aware data and server-side secrets are available from the same platform. You still decide who can access each app, review its code and meet your organisation’s privacy and compliance obligations.
What you keep
Full control where it counts
It's real code
React and TypeScript you can read, edit and review. The agent writes it, and your team can take over at any line.
Your stack, your conventions
Bring your own components, tests and review process. Forge speeds your team up without hiding anything from it.
Fits what you have
A product and customer layer, not a rip-and-replace
Keep the systems your business depends on. SmartLinks handles the part they were never designed for: each physical unit and the person holding it.
Customers and field teams
Scan, tap or open a link on any phone
SmartLinks
Digital twin for every unit: identity, owner, history, apps
Your existing systems
Finance, ERP and CRM stay the record for what they own
Worked example
A fleet of rented and rent-to-own appliances
Coffee machines and fridges placed with customers. One tag on each unit serves the customer, the engineer and the business.
Scan to service
An engineer scans a QR code or taps NFC to see the machine, its service history and open jobs. Specialist RFID workflows can use compatible operator hardware.
Contract status
The customer scans the same tag to see their plan, their next payment and what's covered.
Usage
Readings and events land on the unit's own record, ready for maintenance planning.
Buy out
On a rent-to-own plan, the customer can see their remaining balance and take ownership. The record transfers with them.
Beyond the example
Build the process around the work.
Compose mobile scanning, checklists, item-linked records, cases and server-side actions into a workflow for inspections, stock checks, maintenance or handovers. QR works with camera-equipped devices; RFID needs the supported specialist operator hardware.
See the platform capabilitiesPut your team on the interesting part
Sign in with your SmartLinks account, describe the first app, and review the code it writes.
Start building