PermitOS

Changelog

Track what is released, improved, planned, and required before production.

PermitOS changelog entries reflect real product milestones. Planned work is labeled planned, not released. We do not invent version numbers, dates, or features that do not exist.

Roadmap →
Filter

Released & improved

  1. ReleasedAvailableFoundationv0.1

    Initial PermitOS foundation

    Brand system, marketing foundation, route structure, app shell, and trust language.

    • Marketing site with feature, pricing, about, blog, contact, and integrations routes.
    • Design tokens, blueprint typography, and permit-stamp UI conventions.
    • App shell with protected workspace, navigation, and onboarding scaffolding.
    Read about →Product features →
  2. ReleasedAvailableWorkspacev0.2

    Supabase-backed workspace MVP

    Authentication, organizations, projects, document metadata, rules-only precheck, readiness reports, issues, corrections, activity logs, and settings.

    • Email + password authentication with protected /app workspace.
    • Projects CRUD with organization scoping and activity logging.
    • Document metadata + storage upload, rules-only precheck reports, and issue tracking.
    Open workspace →Docs: workspace →
  3. ReleasedAvailableConsent & Legalv0.3

    Public consent and preference infrastructure

    Cookie consent, unsubscribe, email preference center, suppression list, and legal page structure.

    • Cookie consent banner with granular categories and persisted preferences.
    • Public unsubscribe and email preference center backed by Supabase.
    • Suppression list honored by transactional and marketing flows.
    Email preferences →Privacy policy →

Planned

PlannedPlannedAI

AI document extraction

Document extraction and plan-reading workflows are planned. PermitOS does not claim AI document reading is live until configured.

  • Plan-reading, sheet identification, and field extraction are not yet wired up.
  • When enabled, outputs will be labeled as AI-generated and require human confirmation.
  • No fake AI summaries are shown in the current product.
Roadmap →
PlannedPlannedIntegrations

GIS and local code integrations

Parcel, zoning, and local code integrations require configuration and validation before they are exposed in the product.

  • No official zoning determinations are produced today.
  • Parcel lookups, zoning overlays, and code references are planned per jurisdiction.
  • Each integration will be labeled with its source and last-updated date.
Integrations →
PlannedPlannedDeveloper

Public API and webhooks

API and webhook documentation are planned. No public endpoints, SDKs, or fake integration keys are exposed today.

  • Public REST API surface, signing keys, and webhook delivery are not implemented.
  • Docs will list real, versioned endpoints once available.
  • Until then, integrations are handled per-customer.
Docs →

In setup

These items must be configured and verified before PermitOS is treated as production-ready for any organization. They are not marketing claims.

  • Legal entity configured

    Real registered company name in legal pages, footer, and contracts.

  • Business mailing address configured

    Required for CAN-SPAM, transactional email footers, and legal notices.

  • Legal pages reviewed

    Privacy, terms, acceptable use, and DPA reviewed for this workspace.

  • Email sender configured

    Verified sender domain and a monitored sending identity.

  • Unsubscribe and suppression tested

    Unsubscribe, preference center, and suppression list verified end-to-end.

  • Bounce and complaint processing configured

    Bounce + complaint webhooks update suppression and prevent re-sending.

  • Billing provider configured if charging users

    Tax, invoices, refunds, and dunning handled by a real billing provider.

  • Document security and retention policy reviewed

    Storage scopes, retention windows, and deletion paths documented.

  • AI output disclaimers reviewed

    AI-generated content labeled and never presented as an official determination.

  • Production Supabase RLS tested

    Row-level security tested per role on every workspace table.

  • Storage access policies tested

    Object storage policies verified for read, write, and signed URL flows.