Restaurant ordering that keeps working when the internet doesn't.

Waiter tablets, a dine-in floor plan, kitchen printing, and delivery orders — all on your own Wi-Fi. No cloud bill, no technician visits, and it updates itself. Running daily in 2 restaurants in Chalkida.

Hiring? See my skills & CV →

AlexZaxa Solutions

2 restaurants

running daily, in production

Connectivity

Works offline

your own Wi-Fi, no cloud bill

Updates

Self-updating

updates arrive without a technician visit

Fylakas

24/7

monitored, every live system

A status report, not a highlight reel.

How the pieces connect

tap or click a node
AlexZaxa Solutions Fylakas Anemos Kleidi Skopos Nomos Trading bot Dokimi

Fylakas watches the PDA and Skopos · Anemos updates the PDA · Kleidi licenses it · Dokimi feeds the trading bot · Nomos would unify the rules behind all three — tap or click a node to jump to it

How to get started

  1. 1

    Free demo

    At your restaurant, or online — whichever works for you.

  2. 2

    Setup

    Installed on the Wi-Fi and tablets you already have.

  3. 3

    Ongoing updates & monitoring

    Software updates itself, and Fylakas watches it around the clock.

From €200/month, or €2,600 every 3 years — see pricing →

Live, in production

the tools that operate the featured system

Update distributor

live, in production

Anemos · Άνεμος · the wind

Anemos: pushes a signed update to every restaurant without me visiting.

Every PDA install updates itself without me touching the restaurant's PC.

The signed-update distributor behind the PDA's self-updating software: packages a release, signs it, and lets every live install pull it down on its own schedule. The mirror image of remote license management — the other half of keeping an install healthy.

  • Signs every release before it's allowed to reach an install
  • Runs on the same schedule as the income sync, no separate agent

Uptime watchman

live, in production

Fylakas · Φύλακας · the watchman

Fylakas: tells me the moment the PDA or Skopos goes quiet, not just when they error.

The thing that notices when something else goes quiet.

A small watchman that pings every live system here and alerts the moment one stops answering — the PDA going dark, Skopos falling over. It watches for silence, not just errors; a hang looks the same as a crash to it.

  • Watches every live system here, PDA included
  • Alerts on silence, not just on error

Scope guard

live, in production

Skopos · Σκοπός · the scope

Skopos: stops me from ever testing something I'm not allowed to.

The program's scope document is the only thing allowed to say yes.

A small request gatekeeper built for an active bug bounty engagement: every outbound request gets checked against the program's published scope and rate limit before it's allowed to leave. If a target isn't on the list, or the limit's already spent, the request never goes out.

  • Checks every outbound request against program scope before it's sent
  • Enforces the program's rate limit locally, not just by discipline

How I tend to work

Ship the whole system, not the demo
The PDA isn't just an app — it's the licensing, the update pipeline, and the dashboard that watches it. If I can't operate it after launch, it isn't done.
Fail safe, not silent
A license sync job only acts on a clear signal — any network error or bad response leaves the restaurant running exactly as it was, rather than guessing.
Constraints before code
For the trading bot, the paper-first gates got written before a single order-execution line did. For the bug bounty tooling, the scope and rate limit got read before the first request. The rules come first.
Alexandros Zacharopoulos

About

I build and operate whole systems for clients and employers alike: the product, its licensing, the pipeline that updates it, and the monitoring that watches it after launch. For a restaurant, that means software that doesn't go down when the internet does. For an employer, that means someone who ships and maintains the whole thing, not just a demo. I'm Alexandros Zacharopoulos — AlexZaxa online — IT support and web/Python development out of Chalkida, Greece, with a home lab (Windows Server, Active Directory, Linux, Docker) that's where most of what's above actually started.

Languages: Greek (native), English (fluent)

Python
the PDA, Skopos, Fylakas, Anemos, Dokimi
C#
LiteVoice's desktop client
Flask
the PDA's local, offline-first web server
Windows Server / Active Directory
the home lab's identity and domain layer
Linux / Docker
relay and self-hosted services, including LiteVoice's relay
Networking
the home lab everything above actually runs on
Supabase
the PDA's income sync, licensing, and admin dashboards

Building something that needs to actually keep running? Let's talk.

Don't like forms? Email projects@alexzaxa.com directly.