Skip to main content

Pelagia Demo

A guided entry to the live software

Explore Pelagia in a working environment.

The public demo provides a hands-on view of Pelagia’s browser-based scientific workspace and the processing system behind it. Use this page to understand the shared environment, current hardware, and access level before opening the live instance. N.B. Pelagia is under constant development under a small team; so please forgive changes, downtime, and errors while we work to make it the best we can.

Current demonstration

One shared project, ready to explore.

Available now

General Pelagia demo

Shared access

The launch link supplies the current shared connection details and opens the Demo User in a single demonstration project with Editor access. It is intended for exploring the interface and representative workflows—not for storing research data.

Account
Shared Demo User
Project
Test
Role
Editor
Launch this demo

What to explore

Follow imagery from source to scientific review.

The available data and processing state may evolve, but the demo is designed to show how Pelagia connects high-throughput processing with interactive inspection.

01

Browse source imagery

Move through registered assets and frames while retaining acquisition and processing context.

02

Inspect candidate ROIs

Review detected regions of interest, masks, measurements, and the frames in which they occurred.

03

Track processing

See how jobs, workers, and staged data products support traceable, high-throughput workflows.

Current environment

A substantial shared deployment—not a hardware requirement.

Pelagia can be configured for different data volumes, instruments, and computing environments. These figures describe the resources currently allocated to the public demo and may change as the deployment evolves.

22allocated CPU cores
120 GBsystem memory
~22 TBshared data volume
~900 GBdatabase volume

The current instance runs on Linux with PostgreSQL for durable metadata and project-scoped storage for image products. Pelagia’s background-worker architecture can also distribute processing across additional CPU or dedicated GPU/ML workers when a deployment requires it.

Authentication and permissions

Access can be matched to each collaboration.

Pelagia uses project-scoped sessions so a person’s role can differ between projects. The public demo uses Editor access; managed deployments can assign the other levels when appropriate.

Viewer

Read-only access for browsing project data and reviewing available results.

Public demo

Editor

Viewer access plus permission to create or modify scientific project records and workflows.

Manager

Editor access plus project-scoped user and account management.

Administrator

Project or system administration for teams responsible for the deployment and its users.

Ready to look around?

Open the shared Pelagia instance.

By continuing, you acknowledge that this is a shared, non-production environment. See the privacy notice for information about the Pelagia Studio website and linked services.