Labs enter through a controlled workspace
Team members accept invites, authenticate with Supabase-backed email auth, and land in a workspace built for their lab instead of a generic dashboard.
Labframe connects instruments, artifacts, notes, parameters, and run lineage into one operating surface. Researchers can upload data or attach a live run, keep the full setup intact, and get analysis or troubleshooting without re-explaining the experiment every time.
Team members accept invites, authenticate with Supabase-backed email auth, and land in a workspace built for their lab instead of a generic dashboard.
The onboarding agent captures instruments, experiment families, failure modes, desired outputs, and collaboration needs, then turns them into templates, connectors, and next actions.
Data artifacts, notes, parameters, results, and analysis summaries persist into a shared timeline so later runs have continuity instead of amnesia.
Left rail for intake, center canvas for analysis, right rail for “context in scope” so users can see what the AI is using.
Timeline plus table filters for experiment, status, owner, tags, instrument, and date, with direct links into run detail and comparisons.
Live telemetry and upload-based flows coexist so labs can start with files and graduate to connected instruments without replatforming.
Invite-only access, structured experiment records, private artifact buckets, and workspace-scoped row-level security are built into the implementation.
The new Next.js product layer handles auth, UX, and product APIs while the existing Python stack keeps device communication and ingestion responsibilities.
This repo now includes a deployable `web/` app, Supabase SQL migrations, and import / internal ingest paths for the legacy workbench data.
Use the invite flow if your workspace already exists, or contact founders@labframe.ai to seed a pilot workspace and migrate your first experiment history.