VECTOR Install VECTOR

01 Self-hosted placement operations

Keep each placement
accountable.

Plan cohort coverage, assign students and hosts, verify hours and check-ins, and close every placement with the evidence your process requires.

Start the installation Download v3.4.0 Installation required

You are viewing the public product page. Run VECTOR self-hosted to sign in and use the workspace.

  • School-controlled runtime
  • Explicit role boundaries
  • Open source under MIT
Self-hostedOne school, one controlled installation
Role-scopedAdmin, coordinator, tutor and viewer access
TraceableAppend-only audit events for sensitive actions
PortableValidated CSV and verified backup workflows

02 One operational workspace

See the programme.
Act on the gap.

VECTOR turns coverage, placement progress, follow-ups and evidence into one shared operating picture. The example below uses fictional records and mirrors the real workspace structure.

01

Coverage planning

Find every unplaced student before the period starts.

Filter one cohort and period, expose overlaps, and open a prefilled placement directly from the gap.

02

Attention queue

Start with the work that needs a decision.

Overdue evidence, pending hours, approaching dates and missing assignments arrive in one role-scoped queue.

03

Programme rules

Publish requirements without rewriting history.

Version target hours, check-ins and evidence requirements; each placement keeps the rules it started with.

04

Completion readiness

Close only when the record is genuinely ready.

Verified hours, follow-up and accepted evidence remain visible, deterministic and required before completion.

03 The operating flow

One workflow.
Each decision traceable.

01

Plan the coverage.

See who still needs a placement by cohort and period, then record where the work happens and when.

02

Follow the work.

Verify time, record check-ins and track each required evidence item against the placement it belongs to.

03

Close the record.

VECTOR blocks completion until the required hours, follow-up and documents are in place.

04 Built for real operating conditions

Straightforward to operate.
Explicit where it matters.

Role-aware access
Administrators, coordinators, tutors and viewers see only the work their role permits.
Auditable changes
Sensitive actions leave a trace without copying personal fields into audit metadata.
Portable records
Use bounded CSV import and export when records need to enter or leave the installation.
School-led identity
Set the product name, colours, contact details and logo at runtime for your own installation.

05 Keep the boundary explicit

Student records belong inside your institution’s control.

VECTOR runs as a private Node and SQLite service. It adds no hosted application dependency, no analytics script and no third-party font or interface runtime.

  • 01
    Server-side sessions

    Opaque cookies, origin checks, CSRF protection and inactivity expiry guard authenticated work.

  • 02
    Scoped data access

    Every collection, export and cursor remains bound to the signed-in user’s school role and scope.

  • 03
    Infrastructure-operated recovery

    Infrastructure operators use verified backup manifests; restore, diagnostics and compaction remain host-level commands outside application roles.

Read the security model

06 One system, deliberate permissions

Give each person the view their work requires.

Permissions are enforced by the server, not hidden only in the interface.

ADMIN

School administrator

Owns users, branding, retention and governed corrections.

OPS

Coordinator

Plans coverage, manages programmes and closes operational records.

TUTOR

School tutor

Works only with assigned placements, time, check-ins and evidence.

VIEW

Viewer

Reads the school-wide placement picture in read-only mode.

Dependency-light by designNode 22 / 24 LTS · Express 5 · SQLite · Zod · plain browser modules

View verification history

07 Own the runtime

A public product page.
A private workspace.

VECTOR is designed to be run by the institution that uses it. The browser workspace talks to your own Node and SQLite installation; GitHub Pages only publishes this product presentation.

Before production use, your institution remains responsible for its legal basis, retention schedule, minimisation, DPIA and transport security.

  1. 01
    Configure the boundary

    Set the public HTTPS origin, school identity, time zone and a unique one-shot bootstrap password.

  2. 02
    Initialize once

    Create the empty database and first administrator, then remove the bootstrap secret.

  3. 03
    Serve behind TLS

    Start the hardened container, confirm readiness and test backup restoration before loading real records.

$ cp .env.example .env$ docker compose run --rm --no-deps vector$ remove bootstrap secret · docker compose up -d
Read the complete installation guide Get the v3.4.0 release