Built like an instrument.
Some rules in Advanzio are not features.
The software never lies about state
A reading on screen means the instrument is reporting right now — silence makes the number vanish, never freeze. “Synced” means the other side confirmed. “Loaded” means dispatched, not applied — until the machine itself says applied. Optimism is a bug class, and it is designed out.
Offline is not a fault
Networks fail routinely on real premises; records must not. Every layer assumes disconnection as weather: the machine keeps working, records queue durably where they were born, and everything reconciles — in order, without loss — when the connection returns.
Records hold
A weighing is written once, complete in itself, stamped with everything it was judged against at that moment. Later edits to catalogues or prices cannot quietly rewrite history. Corrections append; nothing is overwritten. The books a business reads are the books it can defend.
The instrument measures; the platform remembers
The approved weighing instrument produces and displays the weight — Advanzio never touches the measurement. Everything Advanzio adds — memory, movement, meaning — sits outside the measurement chain, by design and by principle.
The customer's data is the customer's
No advertising, no behavioural tracking, no resale — ever. Records exist for the business that produced them.
Nothing decorative
If it is on screen, it works. No mock buttons, no coming-soon theatre, no dashboards drawn before the data earns them.
Clean seams, honest custody, native surfaces.
Clean seams, everywhere
Advanzio is built as a core of business logic surrounded by replaceable adapters — the storage engine, the message transport, the scale vendor’s dialect, even the icon libraries in the design system sit behind seams. That is why the platform is brand-neutral over scale hardware, and why no single vendor — including any of Advanzio’s own suppliers — is load-bearing for the customer.
Local first, then the cloud
The apps keep their working data on the device and treat the network as an accelerator, not a dependency. The interface reads from local storage and never blocks on a request. The cloud’s job is custody, coordination, and reach — not permission to work.
Custody end to end
A record travels from the machine’s own durable ledger to the cloud’s, acknowledged at every hop, deleted at the source only when the next keeper has confirmed. Two independent buffers stand between a power cut and a lost weighing.
The fleet updates itself
Firmware moves over the air with a one-boot proving rule: a new version gets exactly one chance to demonstrate health, and failure reverts automatically to the last good version. A machine can miss an update; it cannot be bricked by one.
Isolation by construction; identity kept separate from permission
Each business’s world is walled off in the data layer itself — a request that cannot prove which tenant it belongs to is refused, not quietly widened. Traffic between machine and cloud is encrypted in transit. And a principle we hold structurally: who you are and what you may do are separate concerns — identity is pluggable (an email today; a badge or tag at the machine tomorrow) while authorisation is a layer above it. Per-device cryptographic identity is the direction the fleet is built toward; the seams for it are already in place.
Native on every platform, and unmistakably Advanzio
The apps are written in each platform’s own language — Kotlin and Jetpack Compose on Android, Swift and SwiftUI on iOS — not a single web view wrapped four times. An operator’s phone behaves the way that phone should: the gestures, the type, the motion are the platform’s own. What travels across them is the identity, not the layout — a design dogma we hold as platform-native anatomy, brand-native expression. The result is an app that feels at home in your hand and still, at a glance, reads as one product.
Design is generated, not decorated
Advanzio’s colours and type are computed from small declared seeds through a perceptual colour model, with contrast guaranteed by arithmetic rather than eyeballing. Every surface — web, apps, print — derives from the same seeds. Change the seed, and the whole identity follows, provably consistent.
Verified against reality
The platform is tested where it will live: against physical scales on real benches, with hardware-in-the-loop harnesses, wire-fault simulations, and screenshot-contract tests that pin every reviewed interface. A claim that has not been watched failing is not yet a claim.
Chosen for fitness, named openly.
At the machine
Embedded C on ESP32-class industrial microcontrollers: dual-core and RISC-V variants across the fleet, chosen per deployment for cost and capability, with crash-safe on-flash storage.
On the wire
MQTT over TLS: the industrial-IoT lingua franca, carrying acknowledged, correlation-tracked messages in both directions.
In the cloud
TypeScript services in a strict hexagonal architecture: multi-tenant, event-driven, with tenancy isolation enforced in the data layer and proven in tests.
In hand
Native applications, not wrappers: Kotlin and Jetpack Compose on Android, Swift and SwiftUI on iOS, Rust on the desktop. Each surface looks like it belongs where it runs; the product underneath stays one.
In the design system
A seed-to-token generator built on a perceptual colour model, emitting every platform’s token vocabulary from one source of truth.
In a weighing business, trust is the entire product.
Machines that keep working when the internet doesn’t. Records a customer can stand behind in an audit. A platform no scale brand needs to fear and no vendor can hold hostage. Updates that arrive by themselves and can’t brick a machine. And software whose every screen tells the truth.
Businesses interested in the pilot programme are welcome to write.