$ ./strandline --pilot
Code-review evidence for lab software changes.
Strandline is a self-hosted workflow for bioinformatics and clinical-lab software teams that need tickets, review status, repository evidence, audit events, and exportable pilot records without bringing PHI into the system.
tenant: acme-lab
repos: approved code repositories only
identity: OIDC / Keycloak
audit: ticket + review events
exports: tickets, compliance, analytics
data_policy: no PHI, no sample data
why it exists
Lab code changes need usable evidence.
Spreadsheets, chat threads, and raw Git history are painful when a team needs to show what changed, who reviewed it, what remains open, and where the audit trail lives. Strandline gives the pilot team a focused operational layer for that work.
Review workflow
Track tickets, repository changes, risk status, and review queues in one place.
Audit trail
Record review and ticket events so pilot evidence can be inspected later.
Local deployment
Run with Docker, customer SSO, signed local licensing, and minimal optional heartbeat.
paid pilot
A narrow, self-hosted package.
The first engagement should stay deliberately bounded: one institution or department, one production tenant, a small set of approved repositories, and one SSO path.
What the pilot includes
- GitHub/GitLab repository onboarding
- Ticket and code-review evidence workflows
- Immutable audit trail for review actions
- SSO with customer OIDC or bundled Keycloak
- Local analytics and pilot evidence bundle
- Signed local license for self-hosted deployments
data boundary
Code metadata only.
Strandline is designed for code repositories and workflow evidence. The deployment should not receive patient, sample, or regulated result data.
- > No PHI, patient identifiers, sample data, clinical records, or lab result data
- > Customer owns SSO, repository access, hosting, backups, and network controls
- > Support covers Strandline operation, configuration, upgrades, and product defects
- > Not a legal, regulatory, privacy, validation, or compliance-certification service
acceptance
What “working” means.
A pilot is accepted when the customer can sign in, connect an approved repository, generate audit evidence, export the evidence bundle, and produce a backup artifact.
- [ok] Admin signs in through SSO
- [ok] Approved non-PHI repository is connected
- [ok] Test commit appears in Code Acceptance
- [ok] Audit event is generated from a review action
- [ok] Pilot evidence bundle exports cleanly
- [ok] Backup artifact is produced
$ ./contact --strandline
Want to evaluate Strandline?
Start with a short fit check: deployment environment, SSO path, repository list, PHI boundary, and what evidence your team needs from the pilot.
Contact Bioinformat