Institutions and teams
For departments, research groups and teams that need one rule set.
The workspace models roles, invitations, seat limits and audit export today. Cohort access, teaching deployment and institutional hosting are design intent: they are being shaped with the first departments, and this page says so once so the rest can be specific.
What an institution gets
Four things, stated as intent where they are intent.
- Cohort accessDesign intent
- A cohort of students or a research group onboarded together, with the sample project as a common starting point and each student's work isolated in their own projects.
- Teaching useDesign intent
- A twelve-week module mapped to the eight stages, with the evidence pack as the submission format and the worst fold on page two of every one.
- Reproducible courseworkDesign intent
- Workflows as versioned specifications, deterministic sample data, and a run record that lets a marker re-run what a student ran.
- Workspace standardisationDesign intent
- Teams that want one validation rule set, one method catalogue and one report format, with roles, invitations and audit export.
What ships today
- Roles: owner, admin, quant researcher, analyst, viewer
- Invitations with seat limits; a workspace keeps at least one owner
- Account export as JSON and an audit log with categories
- 119 methods, 43 models, 4 export formats, the same for every seat
- Local-first data: JSON on a machine you control, or PostgreSQL when configured
Supported on-premise or VPC deployment, SSO and SCIM are listed under the planned Institution plan and are not shipped.
Make an enquiry
Answered by a person within five working days. The questions are the ones a cohort needs answered before term starts.
What a marker sees
Page two of every submission: the fold count, the mean, the standard deviation and the worst fold.
The evidence pack is the same for a student and a desk. A section appears only when the work behind it ran, so a submission cannot claim a validation it did not perform.