Platform
How Laridae works.
It's software streaming, built for work that punishes a laptop. The application runs on a cloud workstation; you work in its real interface from wherever you are.
The session path
The application never leaves the workstation.
When you start a session, the application opens on a cloud workstation — its own runtime, its own compute, its own storage and access control.
What reaches you is the picture: the interface, streamed live. What goes back is your input — mouse, keyboard, pen, the peripherals your work depends on.1
Because the work stays out there, so do the project files, the licenses, and the hardware you'd otherwise have to buy. The thing in front of you just needs to show a video and send your clicks.
The environment model
Bodega and Despacho.
Two kinds of environment, matched to how work actually behaves — named in the language of the infrastructure they run on.
Somewhere you come back to. Your files, your application settings, and your working state stay inside the environment between sessions.
- Storage that belongs to the environment, not the laptop
- Access controlled at the boundary you can see
- A stable home for ongoing project work
- Built for daily production and shared project spaces
Compute for one task. You spin it up when the work spikes and let it go when the task is done.
- A render pass that needs more machine than the desk has
- A heavy model check before a coordination meeting
- A one-off simulation or analysis run
- Built for spiky demand without standing hardware
What sits where
The requirements move to the session.
The point of Laridae is that you reach demanding software from the hardware you already own.2 The workstation spec, the GPU question, the storage question — those belong to the environment now, not to every desk.
That changes how you plan. Instead of sizing every machine for the heaviest thing it might ever run, you size environments for workloads and reach them from ordinary devices.
It changes where the work lives, too. Files stay in the environment, under its access controls — which helps when reviewers, contractors, or a distributed team all need the same project without it leaving the boundary.
Where things sit
- Application execution
- Remote environment
- Project files & state
- Remote environment
- Hardware requirements
- Remote environment
- Access control
- Environment boundary
- Display & input
- Your device
What we validate
We prove it workflow by workflow.
Laridae is being validated with early teams. We look at the things that actually decide whether streamed software is workable for you.
1How it feels depends on the application, your workflow, your device, the network, the region, and how the session is set up. We don't claim zero latency or performance identical to a local machine.
2"Any device" is the goal, not a guarantee. Your actual experience depends on the device, browser, operating system, network, and the application's own requirements.
Technical review
Bring your stack. We'll walk it through.
The architecture is open for technical review. We'll take your people through the session path, the environment model, and the access model against your real software list and network.