Introducing Weave: Run Your Android, iOS or Web App Natively on Every Kiosk

Product announcement · Azimut SDK

Your customers know your mobile app. They know where to tap to pay a bill, buy an eSIM or add a roaming pass. Then they walk into a store and meet a kiosk that looks nothing like it, shows last month’s offers and can only take a bill payment.

Today we’re introducing Weave, a feature of Azimut SDK that runs your existing Android, iOS or web app natively on self-service kiosks. Customers get the same look, journeys and offers they already know, and your kiosk payment, ID, SIM and printer hardware stays connected through Azimut SDK. And because Azimut middleware translates every request for your back end, legacy billing and CRM systems work seamlessly with the new frontend.

Why legacy kiosks fall behind

Most operator kiosks were built as a separate product, with their own codebase, their own team and their own release cycle. That creates the same problems almost everywhere:

• Out of date. Offers, prices and branding on the kiosk lag weeks behind the app.
• A few journeys only. Bill payment works, but SIM, eSIM, SIM swap and plan changes still send customers to the counter.
• Built twice. Every change has to be designed, built and tested again for the kiosk.
• Locked to one vendor. Changing hardware means rewriting the application, so old machines stay in service.

Weave removes the second build. The kiosk follows your app.

Two ways to bring your app to the kiosk

Weave works in two modes. The difference is where your app runs.

Weave Mirror: change your app, the kiosk follows

AI-assisted tooling analyses each change in your Android, iOS or web app and applies the same screens and journeys to the kiosk app, rebuilt for the kiosk and its hardware. Every change goes through automated tests and a staged, reversible release, so it reaches a small group of kiosks before the wider fleet.

Weave Mirror keeps your existing kiosk software and runs on one Windows enclave per kiosk.

Weave Embed: your app, running in the kiosk

Your app runs natively on a device inside the kiosk, exactly as customers see it on their phones, so every app release reaches the kiosk when it reaches customers. A Windows enclave in the kiosk keeps card, cash, ID, SIM and printer hardware connected through Azimut SDK.

The trade-off: with Weave Embed, every kiosk journey, including payments, SIM and ID, is built in your app, with Azimut.

	Weave Mirror	Weave Embed
How it works	AI-assisted tooling reads changes in your app and updates the kiosk app	Your app runs natively on a device inside the kiosk
Update speed	Fast: each change is converted, then tested	Immediate: the same release as phones
Existing kiosk software	Kept and reused	Kiosk journeys move into your app
Hardware	One Windows enclave per kiosk	App device plus Windows enclave
Who builds kiosk journeys	Azimut, in the kiosk app	Your app team, with Azimut

Built on the rest of the platform

Weave is one layer of the Azimut platform:

1. Your app stays the source of truth for screens, journeys and offers.
2. Weave brings that app to the kiosk, by mirroring or embedding it.
3. Azimut SDK in the Windows enclave keeps every supported device behind one JSON API.
4. Azimut middleware translates kiosk requests for your systems, from modern REST APIs to legacy SOAP/XML billing, message queues and SFTP document archives. Legacy platforms stay where they are.
5. Satellite stages and tracks kiosk releases and device health across the fleet.

Azimut SDK already runs on more than 1,500 self-service kiosks, including SIM, eSIM, bill payment and top-up kiosks for leading telecom operators. Weave builds on that foundation.

Get started

Weave is available for telecom self-service projects today. Tell us about your app, your systems and your kiosk estate, and we’ll show you what Weave looks like with your journeys.

• Weave for mobile operators
• How Weave works
• Telco kiosk software
• Request a demo