Bleskomat

• Name: Bleskomat
• URL: https://www.bleskomat.com/
• Category: Bitcoin Lightning ATM and payment-terminal infrastructure / open-source device-and-backend stack / non-custodial merchant and educational tooling
• Tags: bitcoin-ecosystem
• Summary: Bleskomat is device-and-operator packaging for Lightning ATMs and terminals. The useful part is the bundle — firmware, backend choice, configuration, fee policy, and hosted-versus-self-hosted operation — not the ATM label. Small operator stack, not a payments anchor.
• What it does:
  • Sells Bitcoin Lightning ATMs, payment terminals, and DIY kits built around offline device operation with customer phones handling the online wallet interaction
  • Offers a Bleskomat Platform subscription for browser-based device configuration, statistics, fee and limit management, and payment-failure notifications
  • Publishes open-source firmware and backend software so operators can continue running devices without depending entirely on the hosted company platform
  • Supports several deployment models for device payment handling, including the hosted Bleskomat Platform, a self-hosted open-source bleskomat-server, and LNbits via a dedicated extension
  • Maintains a broader open-source repo surface that includes ATM firmware, web-serial tooling for browser flashing/configuration, a backend payment server, and a Lightning point-of-sale terminal
• Key claims:
  • The official homepage says all Bleskomat products use the Bitcoin Lightning Network to send or receive bitcoin and argues Lightning gives the products faster payments, lower fees, and better privacy than on-chain transactions
  • That same homepage calls the Bleskomat ATM the “world’s first offline Bitcoin Lightning ATM” and explains that the customer inserts cash, scans a QR code with a Lightning wallet, and the mobile wallet requests payment from the backend server on behalf of the ATM
  • The homepage says operators can update and configure device firmware directly in the browser, receive payment-failure notifications, view statistics, and manage fees and buy limits through the Bleskomat Platform
  • The homepage also says the device firmware and server software are open-source so operators can keep running their ATMs even if Bleskomat the company no longer exists
  • The GitHub organization shows Bleskomat is not just a storefront: it publicly maintains repositories for a DIY ATM, a payment-authorizing web server, browser WebSerial tooling, and an offline Lightning POS terminal
  • The Bleskomat DIY README says the device must be paired with a server for Lightning payments and explicitly lists three options: Bleskomat Platform, the self-hosted open-source bleskomat-server, and LNbits via the Bleskomat extension
  • The Bleskomat Bills firmware README repeats that the ATM is offline, must be paired with payment-facilitation infrastructure, and can be operated via either the hosted non-custodial platform or open-source self-hosted software
• Whitepaper: No canonical standalone Bleskomat whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official homepage, the documentation site, the GitHub organization, and the public device-firmware READMEs; see ../whitepapers/bleskomat-primary-sources-2026-05-02.md.
• Sources:
  • https://www.bleskomat.com/
  • https://bleskomat.github.io/bleskomat-docs/getting-started/index.html
  • https://github.com/bleskomat
  • https://raw.githubusercontent.com/bleskomat/bleskomat-diy/master/README.md
  • https://raw.githubusercontent.com/bleskomat/bleskomat-bills-firmware/master/README.md

Internal linkages

• Best upward comparison points: btcpay-server and lnbits.

Control surface

• Authority sits in device firmware, backend choice, hosted-versus-self-hosted operation, fee and limit policy, and how much of the customer flow gets routed through Bleskomat-managed infrastructure.

• The useful read is device-and-operator packaging. The ATM label is downstream of that.

• Last reviewed: 2026-06-04 UTC