Technical Documentation
Technical overview
Nodo’s layers today: business, Orb, identity, and the plan charge.
Nodo is not a marketplace with a search bar on top. It is a platform with separate contexts that share identity.
Layers
| Layer | Responsibility |
|---|---|
| Business (POS) | Tables, menu, inventory, staff, sales, printer, e-CF. |
| Orb | Interprets voice or text and reads or changes the business within the role. |
| Connectors | Attach a tool to the Orb. One active at a time. |
| Identity | Account, owner / staff, invites. |
| Plan | Internal trial and the owner’s subscription (Stripe on the web). |
Official clients are web (Next.js), app (React Native: iPhone and iPad), and desktop (Tauri). Logic lives in the API.
Principles
- The floor first — the till does not depend on a feed.
- One owner pays — the team inherits access.
- Thin clients — the same API on every surface.
- Little public internals — models, thresholds, and internal names stay unpublished.
Stack (high level)
| Area | Approach |
|---|---|
| API | Node.js service by domain |
| Persistence | PostgreSQL |
| Auth | Session + social providers (Apple / Google) |
| Plan payments | Stripe (Checkout on the web) |
| Printing | ESC/POS on the local network or Bluetooth |
Operational detail (exact models, weights, internal files) is not part of this public documentation.