Technical reference

The application runs remotely.The work stays interactive.

A definitive technical explanation of how Laridae works, what the Group validates, and what to confirm before a workflow briefing.

01 — Session path
Inside a Despacho session.

Remote environment (Despacho)

Cloud workstation

Application execution

visual output →
← input events

Your device

Display and input only

The application executes in the Despacho. Visual output reaches the user's device; input returns to the Despacho. No application code runs locally.

02 — Environment model

The requirements move to the environment.

Bodega

Holds Members, permissions, and the Library

Library

Shared file system for all Bodega Members

Despacho

Streamed application session inside the Bodega

Access

A file open in one Despacho is locked to other Despachos

Display and input

Remain entirely on the user's device

In the current MVP, the Library is accessible to all Bodega Members. Folder- or file-level access controls are not available at this stage.
03 — What the Group validates
Technical fit isevaluated in the workflow.

Early access is a structured evaluation of whether Laridae fits a specific workflow. The Group evaluates across six areas.

01

Application behaviour

Rendering, toolbars, file handling, plugins — evaluated with the real stack.

02

Input fidelity

Mouse, keyboard, stylus, and peripheral input tested against the workflow's demands.

03

Round-trip experience

The practical feel of the visual output and input round trip for the specific application and work.

04

Session stability

How the Despacho holds up across reconnects, network variation, and large project files.

05

Licensing reality

How the application licence maps to the Despacho model — seats, licence servers, and activation.

06

File and process fit

File exchange, storage, handoffs, and how the Bodega/Despacho model integrates with the existing process.

The experience depends on the work.

Performance and access depend on the application, workflow, device, network, region, session configuration, browser, operating system, peripherals, and application requirements. We do not claim zero-latency or local-identical performance. Access from any device is the intended model, not a guarantee. Supported workflows, application compatibility, and access terms can still change.