Three things: the journey the kiosk has to handle (visitor check-in, ordering, payment, token generation, screening…), the sites and a rough number of units, and the hardware and back-office systems already in place. From that we can describe the application, the peripherals it must drive and the integrations it needs. A short discovery call is usually enough to get started.
Every engagement is scoped and quoted individually after discovery. We split the work into the kiosk application, hardware integration, back-office integration, deployment and support, and write a fixed scope against each part so you can see exactly what is included and what is assumed. We do not publish rate cards or package prices — the cost depends on the journey, the peripherals and the number of sites, so a number without a scope would be a guess.
No — AtashiTech is a software company. We write the application and integrate the peripherals, and we work alongside your hardware vendor or system integrator on the enclosure, PC, touch screen and mounting. If you have no vendor yet we can advise on specifications our software is already proven against.
Most of our kiosk applications are native Windows executables, because that is what the widest range of printers, scanners, biometric readers and payment terminals ship SDKs for. We also build Android and tablet-based kiosk apps where the journey is lighter and the hardware is mostly the screen itself.
A native EXE when the kiosk drives peripherals, must keep working offline, or needs lockdown and watchdog restart — which describes most self-service deployments. A web application when the kiosk is essentially a browser in front of an existing web system and the hardware is limited to the screen. We build both, and often pair a native shell with web content so the two are not mutually exclusive.
The application keeps serving from local storage: check-ins, orders and tokens are queued, badges and receipts still print, and everything reconciles with the server when the link returns. Where an action genuinely needs a live connection — a card authorisation, for example — the kiosk tells the user instead of failing silently, and staff can see the queue of unsynced items in the management dashboard.
Usually, yes. If the device has a Windows or Android SDK, a serial or USB protocol, or a documented API, we can integrate it. We test against the physical unit rather than a simulator, so we ask for a loan device early in the project and treat the peripheral work as its own line in the scope.
We work with whatever the system exposes: REST or SOAP APIs where they exist, database views or stored procedures, scheduled file exchange, or a small middleware service that sits between the kiosk and the legacy system. The kiosk is built so the integration layer can change without touching the screens the visitor uses.
Data captured at the kiosk — ID documents, photos, biometric templates, contact details — is encrypted at rest on the device, sent over TLS, and purged from the kiosk once it has synced. Access to the admin and management screens is role-based and audited. Where regulation requires it, the whole stack can run on-premise so data never leaves your network. Our Privacy Policy describes how we handle data ourselves.
Bespoke kiosk applications developed for you are delivered with their source code, and the IP for that custom work is assigned to you on completion of the contract. Our own platforms — the products listed on this site — are licensed rather than sold, and third-party SDKs stay under their vendors' licences. The ownership terms are written into every proposal, not left to be discussed later.
Bug fixes and compatibility updates for the application, support for the peripherals we integrated, monitoring through the central management dashboard, remote content and configuration updates, and a defined response process when a site reports a fault. Hardware repair and replacement stay with the hardware vendor unless we agree otherwise.
Yes. Our kiosk management platform shows the health of every unit — online status, application version, printer paper, error counts — and lets you push content, configuration and updates remotely, with alerts when a kiosk goes dark. It comes with our solutions and can be added to a kiosk application we build for you.
Not answered here? Tell us about the journey, the sites and the hardware you already have.
Ask the kiosk team