← All our workDevice session and command channel
Device controlIn development
Rveta Connector: a Flutter app that pairs a device to a control plane
A standalone Flutter app that pairs a device to a backend control plane, with hardened token handling and a foreground command channel.
StackFlutterLaravel API
- DeviceFlutter appSecure token storage
- SessionDevice pairingToken rotationRevocation handling
- Control planeLaravel APICommand channel (ping, refresh_status)
What works today
- Device pairing against the backend, with a status screen driven by the real session
- Token rotation, with the new token stored securely; tokens are never shown or logged
- Explicit handling of expired, revoked, inactive and suspended tokens and devices
- Actor sign-in and operator sessions against the backend
- A command channel that polls every 30 seconds while the screen is open and runs only ping and refresh_status
How it is built
- Flutter targeting Android, iOS, Windows, Linux, macOS and web; web is limited to control and status screens
- A decision record states that the dashboard controls the connector
- Separate credentials for actor sign-in and for the device, with documented header rules
- Session status is mapped in one place, so screens never show raw errors or authorization headers
Not built yet
- No native gateway runtime yet: the gateway controls are demonstration only
- No VPN, SMS or call runtime
- No background service or WebSocket command runtime
- Remote assist is a separate future capability that needs its own consent, audit and review
Want something built this way?
Tell us what you want to build, fix, or take over.