Grouphead-aware control core
Explicit control phases track idle, heating, ready, brewing, steaming, cleaning, calibration-required, recalibrating, and error states for consistent extraction flow.
Product overview
BeanOps Model 418
The extraction is dialed-in. Your threat model is the problem.
BeanOps 418 is a premium network-connected espresso appliance with explicit machine-state semantics, stable extraction timing, and protocol-rich operator interfaces.
Feature architecture
Portafilter-to-protocol parity
Operators interact through browser, API, and Telnet without drift in shot command behavior or role permissions.
Operational resilience under pressure
Reboot flow enforces persistent recalibration lockout behavior, while bad credentials trigger progressive throttling instead of destructive resets.
Technical specification
| Appliance identity | BeanOps Model 418 |
|---|---|
| HTTP profile | HTCPCP/HTTP semantics with BREW, POST, GET, WHEN, and discovery routes |
| Telnet profile | Operator command console with role-aware command surface |
| SNMP profile | Read-only COFFEE-POT-MIB exposure on UDP 161 |
| Persistence layer | Durable state snapshots and command/event history |
| Network footprint | TCP 80 (HTCPCP/HTTP), TCP 23 (Telnet), UDP 161 (SNMP) |
| BeanMesh profile | HTTP-based peer enrollment, sync, and tiered brew-round orchestration (max 8 machines) |
| Operator access model | Role-aware guest, barista, admin, and beanops command surfaces |
| Update profile | Signed pull-update channel settings with periodic policy-driven checks |
Operational shot lifecycle
- Boot: system initializes with calibration requirements enforced.
- Service: shot operations unlock when machine enters ready states.
- Maintenance: clean/refill/calibrate actions clear service blockers.
- Admin actions: network and profile controls remain role-gated.
Continue to operator and research docs
Move from product overview to practical operator details and security research playbooks in the documentation hub.