Skip to main content

Enterprise

VIA ID doesn't have dedicated enterprise features today — no SSO, no self-hosted Witness, no audit export, no SLA. This page is an honest roadmap, not a feature list: nothing below is available yet, and nothing on viaid.ai claims otherwise.

What "enterprise" would mean for VIA ID​

Given what VIA ID actually does — witness co-signing and tamper-evident logging, not identity or access management — the enterprise-relevant gaps are things like:

  • Self-hosted Witness Service. Today, minting goes through VIA ID's hosted Witness (/api/witness + /api/mint). An org that doesn't want a third party co-signing every badge would need to run its own Witness.
  • Audit / compliance export. A structured export of verification history and badge state for an org's own audit tooling, beyond what a single verify call returns.
  • SSO for any future admin surface. There is no admin dashboard today (badge/download/ contact data lives in Supabase, accessed via the service-role key, not a UI) — SSO would only become relevant once one exists.
  • SLA / support commitments. None exist today; VIA ID is early and pre-widely-used, per its own status note.

What exists today that enterprise evaluators should know about​

  • The Witness Service co-signs with a key held server-side (Vercel + Supabase, service-role key never exposed to the browser) — see the red-team pass that hardened this specific boundary.
  • All privileged writes (badge issuance, download-gate submissions, contact-form submissions) go through least-privilege Supabase RLS policies: the public key can INSERT only, never SELECT/UPDATE/DELETE — see REST API reference.
  • The download-gate and contact-form "is this a real work email" checks are explicitly not security boundaries — see Claims & terminology.

Talk to us​

If your organization needs something on this list sooner than it's built, use the "schedule a demo" option on viaid.ai — that's real signal for what to prioritize.