Laridae

A system for running professional software somewhere other than the machine in front of you. The application executes on a cloud workstation and you work in its real interface.

Early accessDeveloped by Blue Seagull Group

Laridae is one of the systems Blue Seagull Group develops. It exists because the work that matters most to professional teams, such as models, renders, simulations, and imaging, has outgrown the hardware sitting on their desks, while the people who need that work have spread out.

The system moves execution onto infrastructure built for it and leaves you with the interface. What follows describes how it is put together and what we are validating.

System record

Designation: Laridae
Developed by: Blue Seagull Group
Class: Software streaming
Environments: Bodega, Despacho
Infrastructure: United States and Mexico
Status: Early access

1. The application never leaves the workstation

When you start a session, the application opens on a cloud workstation with its own runtime, processing, storage, and access control.

What reaches you is the picture: the interface, streamed live. What goes back is your input, meaning the mouse, keyboard, pen, and the peripherals your work depends on.¹

Because the work stays out there, so do the project files, the licences, and the hardware you would otherwise have to buy.

How it works in detail

The session pathYour application runs in a remote environment with its own runtime, storage, and access control. The picture streams to your device in real time; your mouse, keyboard, and peripherals stream back. Nothing runs on your machine.

2. Two kinds of environment

Some work you return to every day and some you need for an afternoon. Laridae gives you both, and names them for what they are.

Bodega

Persistent

Somewhere you come back to. Files, settings, and working state stay inside the environment between sessions.

Storage that belongs to the environment
Access controlled at a boundary you can see
A stable home for ongoing project work

Despacho

On demand

Capacity for one task. From a despacho you can push a job your desk could not hold, then release it once the job is done.

A render pass heavier than the local machine
A model check before a coordination meeting
A one-off simulation or analysis run

Two kinds of environmentA Bodega is somewhere you come back to: storage, access control, and a stable place to work. A Despacho you spin up for one task: a render, a model check, or a simulation, then let go when it is done.

3. System components

Components of the Laridae system
Ref.	Component	Function
01	Session runtime	Starts and holds the application on a cloud workstation, and keeps the stream and your input in step.
02	Environments	Bodega for persistent project work, Despacho for short-lived task sessions. Each carries its own storage boundary.
03	Storage	Project files and working state belong to the environment rather than to the device you happen to be using.
04	Access control	Who can enter an environment, and what leaves it, is governed at the environment boundary.
05	Application catalogue	The set of professional applications validated for a team, assembled one workflow at a time.

1.How it performs depends on the application, your workflow, your device, the network, the region, and how the session is configured. We do not claim zero latency or performance identical to a local machine.

2.Laridae is in early access, with validation in planning. Supported workflows, application compatibility, and access terms can still change.

4. What Laridae is for

Coverage is organised by the work itself and proved one workflow at a time. Architecture, engineering, and construction is where validation starts.

Workflow coverage Apply for early access

Where to read next