Laridaeby Blue Seagull ComputeRequest early access

Workflows

Coverage by the work, not the logo.

We organize the catalog by what you're actually doing, and we prove it one workflow at a time. Here's what's a focus today and what's a plan — labeled honestly, so you're never guessing.

Architecture, engineering & construction

First validation focus

AEC is where we start.

AEC teams carry some of the heaviest desktop work anywhere — and some of the most spread-out review. Heavy models, distributed people. That's exactly the problem Laridae is built to take on, so it's where we're proving it first.

Below is the work we're validating. Open the model from an ordinary laptop; run the render on compute that appears when you need it; keep the whole project inside one boundary everyone can reach.

A skyline built from stacked blocks, in the Blue Seagull palette.
A1BIM coordinationMulti-discipline models coordinated in one environment, instead of copies bouncing between machines.
A2Architectural designDaily design in the tools your practice already runs, from a project environment that stays put.
A3Model reviewReviewers open the live model from ordinary hardware — no workstation needed to look at heavy work.
A4Rendering & visualizationRender- and playback-heavy passes on remote compute, on demand, without tying up a desk for hours.
A5Structural analysisAnalysis runs sized to the model, in short sessions that exist just for the task.
A6Environmental simulationDaylight, energy, airflow — spiky simulation work on compute that shows up when you ask for it.
A7Distributed reviewSite offices, consultants, and clients working against one environment, inside one access boundary.
A cluster of pixels dissolving outward, in the Blue Seagull palette.

Digital media & creative production

Intended coverage

VFX, 3D, and post.

Creative work runs hot then cold: a quiet week, then a delivery crunch that wants every core it can find. A persistent project environment plus on-demand burst sessions is shaped for exactly that curve.

We're aiming at content creation, editorial, and review — where the feel of the tool matters and the files are big enough that moving them is its own headache.

  • 3D content and lookdev in a persistent environment
  • Render passes as on-demand burst sessions
  • Review and sign-off from ordinary devices
  • Large project files that stay in one place

Scientific research & higher education

Intended coverage

Labs, departments, teaching.

Research groups and departments know the bind: the software is demanding, the hardware budget arrives in bursts, and the people who need the tools turn over every term.

We're aiming at analysis, simulation, and visualization environments you can hand out per lab, per course, or per project — and reach from whatever hardware students and researchers already carry.1

What the work looks like

  • Simulation and analysis on sized environments
  • Visualization of large datasets without local GPUs
  • Course environments that reset cleanly between terms
  • Shared project spaces with defined access
A radiographer at an imaging station, in the Blue Seagull palette.

Radiology & medical imaging

Intended coverage

Research visualization.

Imaging research works with some of the largest interactive datasets in professional computing. We're aiming at research visualization — exploring, rendering, and reviewing imaging data in environments built to hold it.

This is scoped to research. Laridae is not a diagnostic tool, and regulated data has a hard line, stated right here.

Not for diagnostic use. Don't upload confidential, sensitive, medical, regulated, or client-restricted data unless it's separately approved in writing, with the right controls in place.

The catalog

How software gets in.

We build the catalog workflow-first: validate the work, then the applications it depends on — going through licensing, compatibility, and support with the teams who actually use them.

That's slower than printing a logo wall, and more honest. What an application can do here depends on its licensing, its compatibility, and its support — and we'd rather tell you that up front than in the fine print.

Bring your software list

How it goes

  1. A team names a workflow that matters to them.
  2. We map its applications and licensing in an integration review.
  3. We validate behavior, input, and feel in real sessions.
  4. It joins that team's catalog.

†This page describes the workflows we're building toward and validating, not a list of supported products. Specific software availability, licensing, compatibility, and support have to be confirmed. Naming a workflow doesn't imply any application is licensed, validated, or vendor-approved.

1"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.