FREEDOM251

Freedom251 › Kiosk Management Software

Atashi Kiosk Management Platform

Paid APIWebWindows

Visit Atashi Kiosk Management Platform Alternatives Pricing

Atashi Kiosk Management Platform's own site

What Atashi Kiosk Management Platform is

Atashi Kiosk Management Platform gives organizations a central way to monitor and manage kiosk fleets. Its Windows service reports device and application status, peripherals, consumable levels, storage and memory, network quality, errors, and transaction counts. Operators can send content or software updates, view screenshots, collect logs, and restart a kiosk or its application remotely. Updates can be directed to chosen terminal groups, confirmed by devices, and rolled back if a rollout fails. Role- and region-based alerts, scoped access for operators, technicians, and partners, and action records support managed operations. The platform uses MQTT, Azure IoT Hub, SignalR, a REST API, and webhooks, with connections to Power BI, CSV, data warehouses, and ITSM service desks. Kiosks can keep serving users while offline and forward queued telemetry in order once connected. The agent reports operational information; personal or transaction data stays in the kiosk application and its existing back end. Pricing is quoted after scoping, and the platform is offered with customer-specific support terms.

Who it suits

It suits organizations managing kiosk estates across settings such as retail, banking, healthcare, government, and corporate campuses. Third-party kiosk applications need to publish transaction counts and journey errors for the agent to report them.

What it does well

  • Remote content and software updates, restarts, screenshots, and logs.
  • Offline kiosks queue telemetry for ordered delivery when reconnected.
  • Updates can target groups and include a rollback path.
  • Role- and region-based alerts with scoped user access.
  • Exports and connections include Power BI, CSV, and ITSM.

What to know first

  • Paid service; pricing is available on request.
  • Third-party apps must publish transaction counts and journey errors.
  • Windows service requires outbound access to the ingestion endpoint.

Limits

For third-party kiosk applications, the agent can report machine health and queryable peripherals, but transaction counts and journey errors depend on the application publishing them. The custom deployment is scoped to factors including terminal and site count, integrations, hosting and support model.

Plans

PlanBilled and limitsPrice
Custom deploymentQuoted after scoping · Scope depends on terminal and site count, estate ownership, alert rules, integrations, hosting and support modelOn request

As atashitech.com lists them, read 8 Oct 2026. The maker's own page has the final word.

Getting started

  1. Visit the AtashiTech product page.
  2. Request a custom deployment quote and scope the terminal and site count, integrations and support model.
  3. Arrange the cloud deployment and Windows platform coverage.
  4. Install the lightweight .NET Windows service on the kiosks.
  5. Provide outbound network access to the telemetry ingestion endpoint.
  6. Configure the desired alerts, access roles and integrations.

Atashi Kiosk Management Platform is a cloud-based control centre for distributed Windows kiosk estates. It is most suitable for banks, retailers, healthcare providers, public-service networks and other organisations with dedicated operations teams. Its main advantage is combining fleet telemetry, remote intervention and controlled rollouts; its fit depends on the kiosk application exposing the transaction data the organisation needs.

Overview

Atashi is built to manage many terminals from one console rather than supervise individual kiosks. A lightweight .NET Windows service reports uptime, application state, peripheral status, consumable levels, disk and memory use, network quality, errors and transaction counts. That gives support staff a broad view of machine condition and lets them investigate problems without travelling to each site.

The service sends data outbound over MQTT to the ingestion endpoint, so the deployment does not require inbound network ports. A disconnected kiosk continues serving users, stores telemetry locally and forwards it in order when connectivity returns. This preserves local service during an outage, although central monitoring and intervention still depend on network recovery.

Key features

Remote operations

Operators can push content or software releases, capture screenshots, retrieve logs, and restart either an application or the whole machine. These actions cover common first-line recovery and diagnostic work, making the platform more useful than a dashboard that only reports failures. Remote configuration is supported as part of the deployment.

Controlled updates

Software changes can be staged to selected terminal groups instead of sent to an entire estate at once. Device confirmation provides rollout visibility, while a rollback path limits the impact of a failed release. This is particularly valuable for organisations that need a cautious change process across branches or regions.

Access, alerts and integrations

Alerts can be routed by role and region. Operators, technicians and third-party partners receive scoped permissions, and actions are recorded, giving distributed support teams a clearer accountability trail. Integration uses MQTT telemetry, Azure IoT Hub, SignalR, a REST API and webhooks. Transaction and journey counts can be exported to Power BI, CSV or a data warehouse, while ITSM service-desk connections can connect kiosk events to existing support workflows. Retention is set according to the customer's policy.

The agent sends operational telemetry, counts and error events; personal or transaction data remains in the kiosk application and its existing back end. For third-party kiosk software, machine health and queryable peripherals can be reported directly, but transaction counts and journey errors require the application to publish those measures. That dependency matters when selecting the platform for an existing estate.

Pricing

Custom deployment

Custom deployment uses quoted pricing after scoping. The scope and resulting cost depend on terminal and site count, estate ownership, alert rules, integrations, hosting and the support model. This approach suits large or varied estates that need tailored operations, but it gives smaller buyers no published benchmark for budgeting.

Atashi is normally supplied with an annual maintenance contract. The contract covers platform and agent updates, alert-rule changes and an operations support channel, with terms agreed for each customer. Buyers should evaluate those recurring support terms alongside the implementation quote.

Platforms

The management console is delivered through the web, with API access for integrations and a Windows agent on managed kiosks. Deployment is cloud-based, and remote reboot is supported. The documented terminal coverage is Windows, so organisations standardising on Android, iOS or Linux kiosks should look at alternatives instead.

Who it's for

Atashi is aimed at bank and utility networks, restaurant and retail chains, hospitals, industrial sites, government service centres and corporate campuses. It is a strong choice where terminals are geographically dispersed, support responsibilities are shared across roles, and controlled software distribution matters. It is less suitable for a small number of standalone kiosks, or for third-party applications that cannot publish transaction and journey metrics.

Pros and cons

Pros

  • Broad operational telemetry: health, peripherals, consumables, resources, connectivity, errors and counts are visible from one service.
  • Useful remote recovery: screenshots, logs, content and software delivery, plus application and machine restarts, reduce routine site visits.
  • Safer release process: group targeting, device confirmation and rollback support staged updates.
  • Resilient connectivity model: kiosks keep serving users offline and queue telemetry for ordered delivery later.
  • Enterprise integration: APIs, webhooks, Azure IoT Hub, Power BI, warehouses and ITSM connections support existing operational systems.

Cons

  • Windows-only terminal coverage: mixed or non-Windows fleets need another product or an additional management layer.
  • Application-dependent business metrics: third-party kiosk software must publish transaction counts and journey errors.
  • Quoted pricing: cost cannot be compared from a public price list and varies with estate and support scope.
  • Annual maintenance expectation: ongoing updates, alert changes and operations support are tied to customer-specific contract terms.

Alternatives

Kiosk Management Software is the broader category page for comparing kiosk tools. Choose Kiosk if you want a free, open-source PDF reader across a wide range of platforms rather than fleet operations. SureAsset fits buyers seeking free asset lifecycle and licence tracking with API automation. KioskCore is a freemium option for up to two devices with seven-day metric history and limited captures and alerts. OpenKiosk is a free MPL-licensed open-source choice for Linux, macOS and Windows. Libki is a free open-source kiosk management system. KioskSide is a paid alternative for Android, Linux, web and Windows. Kiosker suits Android and iOS deployments with a seven-day trial and subscriptions from $6.99 a month. Moki is a paid Android, iOS, web and API option with per-device monthly billing, 500 API calls per hour per account and a ten-user account limit before additional user charges.

Verdict

Choose Atashi for a professionally operated Windows kiosk fleet that needs detailed health monitoring, remote recovery, staged releases and connections to reporting or service-desk systems. Its main reason to look elsewhere is the combination of Windows-only coverage, application-side metric requirements and custom pricing with customer-specific maintenance terms.

Verdict

Atashi combines fleet monitoring with remote actions and controlled update rollouts. Buyers should confirm scope, integrations, and support terms for their estate.

Questions

How is Atashi Kiosk Management Platform priced?

It is a paid custom deployment, quoted after scoping. Scope depends on terminal and site count, estate ownership, alert rules, integrations, hosting and support model.

Which platforms does it cover?

The listed platform coverage is Windows. The platform is also described as available through web and API.

Can kiosks keep working offline?

Yes. Kiosks continue serving users while disconnected, and telemetry is queued locally for ordered delivery when connectivity returns.

What integrations does it support?

It uses MQTT telemetry, Azure IoT Hub, SignalR, a REST API and webhooks. It also supports Power BI, CSV, data warehouse and ITSM service-desk connections.

Does the agent handle personal or transaction data?

The agent sends operational telemetry, counts and error events. Personal or transaction data stays in the kiosk application and its existing back end.

What support comes with the platform?

It is normally offered alongside an annual maintenance contract covering platform and agent updates, alert-rule changes and an operations support channel. Terms are agreed per customer.

Facts from Atashi Kiosk Management Platform's own pages

Alerts and access
Alerts can be routed by role and region, while operators, technicians and third-party partners receive scoped role-based access and actions are recorded. · atashitech.com, 8 Oct 2026
Analytics and retention
Transaction and journey counts can be exported to Power BI, CSV or a warehouse, and the retention period is set to the customer's policy. · atashitech.com, 8 Oct 2026
Company location
AtashiTech lists Bengaluru, India as its location. · atashitech.com, 8 Oct 2026
Data handling
The page says the agent sends operational telemetry, counts and error events, while personal or transaction data stays in the kiosk application and its existing back end. · atashitech.com, 8 Oct 2026
Headquarters
Bengaluru, India · atashitech.com, 28 Sept 2026
Integrations
The platform uses MQTT telemetry, Azure IoT Hub, SignalR, a REST API and webhooks, and supports Power BI, CSV, data warehouse and ITSM service-desk connections. · atashitech.com, 8 Oct 2026
Intended users
The page describes use for bank and utility networks, restaurant and retail chains, hospitals, industrial sites, government service centres and corporate campuses. · atashitech.com, 8 Oct 2026
Limit with existing software
For third-party kiosk applications, the agent can report machine health and queryable peripherals; transaction counts and journey errors require the application to publish them. · atashitech.com, 8 Oct 2026
Network access
The Windows service publishes over MQTT and needs outbound network access to the ingestion endpoint, with no inbound ports required. · atashitech.com, 8 Oct 2026
Offline behavior
The kiosk continues serving users when disconnected; telemetry is queued locally and delivered in order when connectivity returns. · atashitech.com, 8 Oct 2026
Purpose
The platform monitors and manages kiosk fleets from a central console, including device health, remote updates, alerts and usage analytics. · atashitech.com, 8 Oct 2026
Remote actions
Operators can push content or software releases, capture screenshots, retrieve logs, and restart an application or machine remotely. · atashitech.com, 8 Oct 2026
Support
The platform is normally offered alongside an annual maintenance contract covering platform and agent updates, alert-rule changes and an operations support channel; terms are agreed per customer. · atashitech.com, 8 Oct 2026
Telemetry
A lightweight .NET Windows service reports uptime, application state, peripheral status, consumable levels, disk and memory, network quality, errors and transaction counts. · atashitech.com, 8 Oct 2026
Update rollout
Updates can be staged to selected groups of terminals with device confirmation and a rollback path if a rollout fails. · atashitech.com, 8 Oct 2026

Where Atashi Kiosk Management Platform stands on Freedom251

Look at these too