Skip to content

Changelog

What has changed

Oldest at the bottom. Every entry describes something you can go and look at in the portal.

Releases

  1. v2.1 September 2026

    Integrations and credibility

    Everything a client needs to check the portal for themselves.

    • A Trust page that measures the portal live instead of describing it
    • CSV exports for the audit log, teams, tools, accounts and any share
    • An ICS calendar feed of access end dates, for Outlook and Google Calendar
    • Personal API tokens for scripts and tools, hashed at rest and revocable
    • Signed outbound webhooks with a delivery log, so alerts reach Slack or Teams
    • Global search across tools, teams and people
    • A refined design system: hairline surfaces, tabular numerals, one button set
  2. v2.1 September 2026

    The demo, and audience rights

    Seven days of everything, then a plan - and rights that manage people, not tools.

    • A 7-day demo on every new account: every published tool, no card
    • When the demo ends, access ends - and nothing is deleted
    • Only an administrator adds, edits, archives or deletes a tool
    • Share rights are about the audience: share further, manage rights, see the log, remove access
    • Running a team is a subscriber's feature; staff can always do it
    • Public trust page, changelog, health check and API documentation
    • CSV exports, an ICS feed of access end dates, and signed webhooks
  3. v2.0 September 2026

    Team sharing

    Tools move between people, with rights and a history.

    • An 8-character share code on every account, generated automatically
    • Teams with their own members, tools and policy; a person can be in many
    • A team-level policy plus per-person exceptions
    • A per-tool activity log with field-level before and after
    • Version history with one-click rollback
  4. v1.0 2025 - 2026

    The private tool portal

    An administrator uploads a tool, the portal checks it, only the right people can open it.

    • In-request audit in a real browser: errors, screenshot, size, validity
    • The tool's own login is removed, so there is one login for everything
    • Files stored outside the web root; served only through a checked door
    • A SHA-256 fingerprint verified on every single open
    • Plans, grants with optional end dates, and a system-wide audit trail
Curious how any of this is guaranteed? The trust page names the test behind each promise.