POS2 is built for restaurants and venues that want:

• One place for everything — Orders, tables, reservations, menu, and payments in a single stack.
• Customer ordering without apps — Guests scan a table QR code, browse the menu, place orders, and pay with Stripe. Optional table PIN keeps ordering secure.
• Real-time updates — Order status (pending → preparing → ready → delivered → paid) flows to staff and customers over WebSockets.
• Multi-tenant from day one — Each restaurant (tenant) has isolated data, settings, and Stripe configuration.
• Self-hosted — Run on your own server or local network; no vendor lock-in.

The frontend is Angular; the backend is FastAPI with PostgreSQL and Redis. All major flows are implemented and documented (see ROADMAP.md and the docs/ folder).

The staff dashboard gives quick access to Catalog, Reservations, Kitchen display, Reports, and more.

More screenshots (orders, kitchen display, reports, customer menu) are listed in docs/screenshots/README.md.

Planned but not yet implemented: batch order operations, and stricter “must pay before continuing” flow. See ROADMAP.md.

• Frontend: Angular 21+ (SPA)
• Backend: FastAPI, SQLModel ORM
• Database: PostgreSQL 18
• Cache / pub-sub: Redis 7
• Real-time: WebSocket bridge (custom service)
• Payments: Stripe
• Deployment: Docker Compose, HAProxy

The quickest way to try POS out is to head over to https://satisfecho.de/ and set up your restaurant.

• Docker and Docker Compose
• Git

1. Clone the repository

   git clone https://github.com/satisfecho/pos
   cd pos

2. Configure environment

   cp config.env.example config.env

   For local development the defaults are fine. For production or a custom domain, set API_URL, WS_URL, CORS_ORIGINS, and SECRET_KEY. See docs/0004-deployment.md.

3. Start all services

   • Local (development): docker compose -f docker-compose.yml -f docker-compose.dev.yml --env-file config.env up -d
   • Production (e.g. amvara9): docker compose -f docker-compose.yml -f docker-compose.prod.yml --env-file config.env up -d

4. Find the app URL
   Run docker compose -f docker-compose.yml -f docker-compose.dev.yml ps (or with .prod.yml if you used prod) and check the PORTS column for the haproxy service (e.g. 0.0.0.0:4202->4202/tcp or 0.0.0.0:4203->4202/tcp). The host port (4202 or 4203) is your app URL.

   • App (recommended): http://localhost:4202 (or the port shown for haproxy)
   • API docs: http://localhost:4202/api/docs
   • Health: http://localhost:4202/api/health

5. Create an account
   There is no pre-seeded user. Open http://localhost:4202/register (use your actual port), enter tenant name, email, and password. The first user becomes the tenant owner. Then sign in at the main URL.

If your frontend port is different (e.g. 4203), replace 4202 with that port. See AGENTS.md for how to detect the port and debug with logs.

Key variables in config.env (see config.env.example for the full list):

Stripe keys are configured per tenant in Settings in the admin UI. Settings also include business profile, contact (phone, email, address, Tax ID, CIF), opening hours, and payment options. For deployment on a domain or IP, see docs/0004-deployment.md.

Browser → Frontend (Angular) → Backend (FastAPI) → PostgreSQL
                                    ↓
                               Redis (pub/sub)
                                    ↓
                          WebSocket bridge → Browser (real-time)

Services (Docker Compose):

• haproxy — Single entry point; routes / to frontend, /api to backend, /ws to WebSocket bridge. Port from FRONTEND_PORT (default 4202).
• front — Angular SPA (dev server in container).
• back — FastAPI app (Uvicorn).
• ws-bridge — WebSocket server; subscribes to Redis and pushes order updates.
• db — PostgreSQL 18.
• redis — Cache and pub/sub.

• Port: docker compose -f docker-compose.yml -f docker-compose.dev.yml ps → PORTS for haproxy → use that host port in the browser.
• Logs: docker compose -f docker-compose.yml -f docker-compose.dev.yml logs -f (all); same -f list with logs --tail=50 back, logs --tail=80 front, logs --tail=30 haproxy.

See AGENTS.md for more detail.

Migrations live in back/migrations/ and run automatically on backend startup.

• Apply manually: docker compose -f docker-compose.yml -f docker-compose.dev.yml exec back python -m app.migrate
• Check pending: docker compose -f docker-compose.yml -f docker-compose.dev.yml exec back python -m app.migrate --check
• New migration: Use timestamped names, e.g. back/migrations/YYYYMMDDHHMMSS_description.sql. See back/migrations/README.md.

Do not edit existing migration files; add a new migration to change schema.

• Frontend and backend both reload on code changes when run via Docker Compose.

docker compose -f docker-compose.yml -f docker-compose.dev.yml --env-file config.env down

• Languages: English, Spanish, Catalan, German, Chinese (Simplified), Hindi (see front/public/i18n/*.json).
• Currency: Per-tenant (e.g. EUR, USD, MXN, INR, CNY, TWD).
• Language picker: In admin sidebar and on the public menu.
• API: Use ?lang=es (or other code) for localized API messages.

See docs/0012-translation-implementation.md.

• Staff: Sign in → Reservations in the sidebar. List, create, edit, seat at a table, finish, or cancel. Tables canvas shows status Reserved (amber) when a reservation is assigned.
• Public: Book at /book/:tenantId (e.g. http://localhost:4202/book/1). After booking, use the link to view or cancel at /reservation?token=.... No login required.

Details: docs/0011-table-reservation-user-guide.md.

For a custom domain or IP, set in config.env:

• API_URL and WS_URL to your backend base URL (use https:// and wss:// for production).
• CORS_ORIGINS to your frontend origin(s).

Then restart: docker compose -f docker-compose.yml -f docker-compose.dev.yml --env-file config.env up -d.

Full guide: docs/0004-deployment.md.

• Done: Order management, reservations, table PIN, Stripe, WebSocket, i18n, deployment docs. See ROADMAP.md for the full list.
• Planned: Order Phase 4 (batch, audit, item replacement), optional stricter “immediate payment” enforcement. Rate limiting and security hardening are described in ROADMAP.md.

• Production: Set a strong SECRET_KEY and REFRESH_SECRET_KEY in config.env.
• CORS: Set CORS_ORIGINS to your real frontend origin(s); avoid * in production if possible.
• Database: Use strong credentials; do not commit config.env.
• Stripe: Use live keys in production and configure them per tenant in Settings.
• Rate limiting: Not yet implemented for most endpoints; PIN attempts are rate-limited. See ROADMAP.md for the planned strategy.

More: docs/0004-deployment.md and AGENTS.md.