Your workspace

Choose an experiment

Open both sides of a QKD application and watch shared key material create a secure result.

Checking services…Portal, relay & KMS gateway

Private rooms

Your sessions

Help centre

From first login to shared keys

A practical guide to starting experiments, inviting another participant, and recovering a session when something stops responding.

Quick start

Run an experiment in three steps

1

Start a private room

Choose an experiment on Playground and select Start session. The portal launches isolated Alice and Bob processes for that room.

2

Invite your partner

Share the room's invite code. Your partner signs in, enters it under Join with invite code, and sees the same session.

3

Open both roles

Open Alice and Bob in separate tabs. Both roles share the room's relay channel and selected KMS key stream.

Sessions

What belongs to a room?

AliceShared relayBobSession-specific KMS backend

Every room has its own identifier, invite code, app processes, and KMS context. Users may share infrastructure without sharing keys or messages between rooms.

Owners can stop and delete a room. A participant who joined someone else's room can remove it from their own list without affecting the owner.

Troubleshooting

Common recovery steps

Waiting for peer: Confirm Alice and Bob were opened from the same room. Reopen either role from the session card if its tab was closed or disconnected.
KMS transport timeout: A low key-generation rate can mean there is not enough material yet. Wait for the room's buffer to refill, then retry the operation.
Interrupted or failed session: Start a fresh room when needed, then use Clean up inactive to remove the old entry.
Missing app or KMS controls: Access is permission-based. Ask a portal administrator to enable the application or KMS control room for your account.

Local development

Running without the portal

Each application remains independently runnable. Start its relay/relay.sh, then launch client/alice.sh and client/bob.sh. These fixed-port tools do not require a portal account.

About LinQ

Quantum security you can explore

LinQ Playground brings QKD-backed applications, a shared relay, and an observable mock key-management service into one approachable research environment.

The project

Learning by running both ends

The playground is designed for demonstrations, teaching, and experimentation. It keeps Alice and Bob visible, lets participants see how shared quantum-derived material affects an application, and makes the supporting infrastructure easy to inspect.

Room isolationSeparate relay and KMS contexts for every portal session.

Observable systemsKey rates, buffers, usage, and session state remain visible.

Standalone firstEvery application still runs locally without the portal.

Research environment

Built for exploration

LinQ is an experimental playground, not a production cryptographic service. Configuration controls intentionally make delays, limited key supply, and failure modes visible so they can be studied.

Administration

Playground operations

Accounts, onboarding, infrastructure and usage in one operational workspace.

Infrastructure

Service health

Checking…

Access control

Registered users

0 usersExport CSV

Search Status Signup App access

						Manage

A shared space for
QKD applications.

Sign in to your workspace

Choose an experiment

Your sessions

Lab tools

KMS control room

From first login to shared keys

Run an experiment in three steps

Start a private room

Invite your partner

Open both roles

What belongs to a room?

Common recovery steps

Running without the portal

Quantum security you can explore

Learning by running both ends

Built for exploration

Playground operations

Service health

Registered users

Signup codes

Connection

Current reservation

Launches

Recent activity

Edit access

Default applications

Create signup code

Change permissions

User activity

User sessions

Manage user

Change password

A shared space forQKD applications.

Sign in to your workspace

Choose an experiment

Your sessions

Lab tools

KMS control room

From first login to shared keys

Run an experiment in three steps

Start a private room

Invite your partner

Open both roles

What belongs to a room?

Common recovery steps

Running without the portal

Quantum security you can explore

Learning by running both ends

Built for exploration

Playground operations

Service health

Registered users

Signup codes

Key management systems

Connection

Current reservation

Usage telemetry

Launches

Recent activity

A shared space for
QKD applications.