Cloud & Local Machine¶
DiKAS can run in a split setup: a cloud instance handles online functions (web shop, reservations, online payments), while the local machine at the venue controls the hardware — receipt printer, kitchen display, card terminal, and TSE fiscal device.
This setup is optional. Businesses running DiKAS purely on-premises do not need a cloud configuration.
What runs where?¶
| Area | Cloud ({name}.next.dikas.de) |
Local (venue) |
|---|---|---|
| Online ordering / web shop | ✓ | — |
| QR table self-ordering | ✓ | — |
| Table reservations | ✓ | — |
| Online payments | ✓ | — |
Guest apps ({name}.order.dikas.de) |
✓ | — |
| Receipt printer | — | ✓ |
| Kitchen display (KDS) | — | ✓ |
| Card terminal | — | ✓ |
| TSE / fiscal device | — | ✓ |
| Master data & reports | ✓ (central) | ✓ (synchronised) |
TSE is always local
The TSE (Technische Sicherheitseinrichtung, fiscal security device) is legally tied to the local POS. There is no TSE in the cloud — receipts are stored there temporarily and signed only on the local machine. For more details: TSE & Tax Authority
Card terminal: direct or via the hardware agent
DiKAS includes its own card terminal integration (ZVT) — no third-party tool required. If the server can reach the terminal directly over the network (local/on-premises), DiKAS communicates with it directly. In cloud mode a hardware agent in the venue network handles all terminal communication (payment, void, refund, settlement) and also reports transactions triggered directly at the device back to the POS. Features & operation: Card Payment · Technical details & failover: Hardware Agent & Cloud Failover
Instant Relay¶
To ensure online transactions reach the local hardware without delay, there is a direct connection between the cloud and the local machine ({name}.lo.dikas.de). As soon as a new transaction is created in the cloud, it is forwarded immediately — before the database sync even runs.
Which transactions are relayed?¶
| Transaction | What happens locally |
|---|---|
| Online order / delivery or pickup | Kitchen ticket printed (optional: bell signal) |
| QR table instant order | Kitchen ticket printed for the order batch |
| Receipt / invoice | TSE signs the receipt; receipt with TSE QR code is printed |
| Table reservation | Audible alarm on the local device (configurable) |
Kitchen display and table view
Replicated orders appear instantly on the local kitchen display and in the table overview — without delay. The local machine updates its display as soon as an incoming change arrives.
Database Sync¶
The cloud and local machine continuously exchange data (bidirectional replication). All master data, orders, receipts, and settings are synchronised automatically.
The relay only speeds up the hardware action (printing, signal, TSE signing). The actual data always travels via the sync.
Offline Behaviour¶
If the local machine is temporarily unreachable:
- The cloud continues operating normally — orders, reservations, and online payments are still accepted.
- New receipts are stored in the cloud but not signed (the TSE is only on the local machine) and not printed.
- Nothing is buffered for later signing — receipts created during the offline period remain unsigned.
- Once the local machine is back online, new transactions work normally again: printing and TSE signing resume.
Unsigned receipts
Receipts created in the cloud during an offline period of the local machine carry no TSE signature. Extended TSE outages must be reported to the tax authority. DiKAS logs all outages automatically (→ TSE Outage).
Frequently Asked Questions¶
Do I have to use the cloud? No. DiKAS works fully on-premises. The cloud connection is only relevant for businesses that want to offer online ordering, QR self-ordering, or reservations over the internet.
How quickly do online orders reach the kitchen? Typically within seconds — the relay sends the order directly as soon as it arrives in the cloud.
What happens if the relay fails? The database sync continues to run. Orders still reach the local machine, with a slight delay via the sync.
Can I run my own cloud instance? The cloud infrastructure is operated by DiKAS and included in the subscription. A self-hosted cloud installation is not currently supported.