Redesigned Account Emails
Verification, password reset and sign-up emails have a new, cleaner layout that follows your mail app's light or dark theme.
Recent updates, release notes, and version history across ApiVault products.
Verification, password reset and sign-up emails have a new, cleaner layout that follows your mail app's light or dark theme.
New accounts and projects get a generated avatar instead of a plain initial, and a button on the avatar in settings swaps it for another.
On small screens, a long linked project or Worker name is cut short instead of running past its card.
A linked project's sync status is now a dot on its avatar, and connection headers drop the project count the list already shows.
The Cloudflare mapping grid now shows it is loading, and the note under a linked Worker lines up with the card.
Approving Cloudflare accounts that are already connected no longer changes your connections.
Connecting another Cloudflare account with the same login now adds it next to your existing connection instead of replacing it.
Connect Cloudflare and keep a Worker's secrets, Previews secrets and build variables in step with your project's keys, with the same previews, retries and strict ownership as Vercel and Supabase.
Every account and project page now loads with a placeholder shaped like the page itself, so content no longer jumps into place when it arrives.
Project Settings now has a Leave Project section, so you no longer have to find yourself in the Members list to leave.
The custom vault key dialog no longer stacks Generate and Copy as extra buttons on the field label.
Vault Encryption and Integrations now draw their headers, notices and key fields from the same shared components.
The environment choice in the Save Key dialog matches the Single / Bulk toggle.
Every dialog now shares the same spacing, error style, buttons and mobile layout.
The Vault Encryption page is now a short list of settings, led by a single Use your own vault key switch.
Changing a project's slug now keeps you on that project's settings page instead of sending you to a broken /user/... URL.
Notification icons and titles line up in every row, and unread notifications are easier to spot.
The sign-up form keeps the suggested username in step with the full name as you type.
Automatic integration entries in the logs show the Vercel or Supabase logo instead of the service-token key icon.
The sidebar can now be hidden on desktop to give pages the full width, and it stays hidden until you bring it back.
`apivault logs --source` documents the service and integration sources.
Work an integration runs on its own now has its own Integration source in the audit log, separate from service tokens.
Integration entries in the log details panel now read as plain labels instead of raw fields.
Audit logs can be filtered by Vercel or Supabase, each integration event has its own checkbox, and PATCH requests can be filtered by method.
Supabase links now show which ApiVault environment they sync and where it goes, as two labeled cells.
Unlinking a Vercel project after Vercel revokes access no longer waits for a retry that can't happen, and keys saved without an environment now reach Vercel.
Linking a project before it has any keys now shows its environments, and the Vercel project picker points to where you choose which projects ApiVault can see.
Several ApiVault projects connected to the same Vercel team no longer delete each other's variables or uninstall ApiVault for each other.
Disconnecting Supabase from one ApiVault project no longer cuts off other projects connected to the same Supabase organization.
Disconnecting Vercel or Supabase after the platform stopped accepting ApiVault now offers Remove anyway instead of waiting on a cleanup that can't run.
Supabase organizations and linked projects on the Integrations page have their own icons instead of the Supabase logo.
Sync errors for Vercel and Supabase only say a sync will retry when one will, and opening a sync preview records a single entry in the audit log.
Push a project's keys into Supabase Edge Function secrets: connect an organization, link its projects, choose the environment each one receives, and ApiVault keeps them in sync.
The Integrations page has a new look: a provider catalog, a separate page for Vercel connections, richer project cards and clearer link, sync and details dialogs.
Fixes found running the CLI under a service token in CI: `run` and `env export` follow the token's environment pin, and no command hangs on a prompt when there is no terminal.
Connecting Vercel now returns you to the project's Integrations page instead of leaving you on Vercel.
When ApiVault is removed on Vercel's side, unlinking its projects now just clears the link, because Vercel has already deleted the variables ApiVault created.
Connect a project to Vercel and ApiVault keeps its environment variables in sync with your keys — automatically on every change, or on demand with a preview.
The homepage now answers the questions developers ask before trusting a vault and describes encryption the way it actually works.
Links to a release or a docs page now unfurl on X, Discord, and Slack with a card showing the page's own title, summary, and date.
Service badge colors now come from each service's own logo and stay readable in both light and dark themes.
Keys now carry their service's brand logo, and the dashboard picks the service for you as you type a key's name or paste its secret.
MCP clients without a built-in icon now get a real logo on the consent screen and in MCP settings, looked up from the client's registration details.
The screen for a project you can't open now shows your project switcher in the header, so you can jump straight to one of your own projects.
Addresses like /settings/test and /docs/getting-starteds now show the site's not-found page with a real 404 status, instead of a project access message or a blank “Not Found”.
Refreshing a project's Logs page no longer flickers between the loading skeleton and your logs several times before it settles.
Accounts whose username is filled in for you — Google sign-in, or registering without choosing one — can no longer end up named docs or dashboard, which made their own projects unreachable.
Links such as /dashboard/logs now open that section of your active project instead of an error screen.
The Service Tokens page and its create dialog are now built from the same components as the rest of the dashboard, which also fixes the rounded corners and panel backgrounds that were missing from them.
Projects can now issue machine credentials for pipelines that cannot open a browser — scoped, optionally pinned to a single environment and a set of IP ranges, and expiring by default.
The CLI now authenticates from APIVAULT_TOKEN, so `apivault run` works in a pipeline with no browser and no stored device token.
Opening a project you are not a member of now explains itself instead of bouncing you to /dashboard without a word or dropping you on the 404 page, and every error screen picked up the redesigned 404's look.
The not-found page now carries the site header and footer, leads with the status code, and tells you which path failed instead of stranding you on a bare block of centred text.
Dialogs are now real dialogs with a focus trap, every form field is properly labelled, the MCP consent screen shows where it is about to send you, and the landing page stops downloading a screenshot it never shows.
The logs endpoint now honours explicit HTTP status codes, can find a single entry by its ID, and rejects an unrecognized status filter instead of quietly returning everything.
View, filter, inspect, and stream real-time audit and request logs for your ApiVault projects directly from the terminal.
The MCP documentation and the agent skill now state that a rejected tool call is recorded in the project's audit log, so an agent has a reason not to retry a vault key the user has not confirmed.
HTTP status codes in the audit logs table now display distinct semantic accent colors and bold monospace styling instead of appearing monochrome white.
Denied reveals, wrong vault keys, throttled requests and forbidden writes are recorded alongside the successful ones, each with the reason it failed.
The vault-key attempt limit now covers the MCP tool surface as well as the web and CLI endpoints, and any API call may identify its project by slug instead of only by ID.
The CLI now knows when this device's token expires, warns you before it does, and explains what to do when a request is rejected instead of printing a bare “Unauthorized”.
Wrong vault keys are now rate limited on every MCP tool that accepts one, and the server reports its real version to the API instead of a hardcoded string.
Brute-force limits on every credential check, a nonce-based Content Security Policy that refuses injected scripts, expiring CLI tokens, and a migration history that once again matches the schema.
Streamlined the empty vault screen with a clean, minimal design featuring direct Add Key and Import .env actions, along with a dedicated filter zero-state.
Introduced an in-app notification center accessible from the user dropdown header, providing real-time alerts for project invitations, security events, CLI/MCP authorizations, and system updates.
Bind project context and CLI settings directly to your local project directory via .apivault.json, eliminating the need to switch projects when changing directories, while retaining global fallback configuration.
Comprehensive real-time audit logging for workspace projects with strongly-typed event stream, incremental live streaming, MCP agent & OS tracking, and SIEM / ECS exports.
Added an API Key filter to the project logs sidebar with instant search and per-key event counts.
Replaced all remaining built-in native checkboxes with the custom Checkbox component in the project settings and modals.
Replaced the built-in select elements with our custom Select component in the add/edit API key modal.
Improved the timeline filter with quick preset buttons for 1h, 2h, 5h, 24h, Today, 7 Days, and 30 Days.
Refined the project .env export workflow with a cleaner, tab-based UI for switching between file downloads and CLI commands.
Redesigned the Export Project .env modal with interactive environment cards, key count indicators, value masking, and one-click copy/download actions.
You can now export a project's API keys directly as a .env file from the keys dashboard.
Officially shipped Multi-Project Workspaces, Role-Based Access Control (RBAC), and Real-Time Audit Logs.
Added the ability to export audit logs as CSV or JSON for SIEM ingestion and compliance archiving.
Remote MCP access now remains bound to an active project membership and enforces project write roles.
Reduced `apivault keys get <id> --reveal` to one API request.
Removed redundant dashboard key-list loads and let a reveal response supply the metadata needed by the CLI.
Introduced Live Tail streaming mode for the Activity Trail to automatically refresh incoming logs, plus enhanced the Log Inspection Drawer with structured action metadata.
Fixed request logger metadata extraction for IP addresses, User-Agents, and latency tracking, plus redesigned the Log Inspection Drawer with a sleek grouped-list design.
Introduced a slide-over inspection drawer for request & audit logs, offering deep insights into endpoints, query parameters, network origins, device/tool identifiers, latency metrics, and JSON payloads.
Enforced server-side permission checks across all API key mutation endpoints to ensure read-only viewers cannot create, modify, or delete secrets.
Refined the member role selection popover to be cleaner and more intuitive.
Added the ability to reset a project to its default state, wiping all keys and resetting encryption without deleting the project.
The CLI now uses the dedicated GET /api/keys/[id] endpoint for individual key operations, reducing payload size and improving request logs.
Added a new Request Logs page to the project dashboard to track all API requests.
Fixed a bug where revealing or copying a key after switching projects would fail with 'Could not reveal that key.'
Introduced a dedicated, full-screen project onboarding flow for new users to create their first workspace.
Automatically generate a unique username based on the email address when users sign up via Google.
MCP connections can now be bound to specific projects during authorization, automatically isolating AI agent access to targeted workspaces.
The ApiVault CLI now natively supports multiple projects with a new projects command group and a global --project flag.
Introduced granular project roles (Admin, Editor, Viewer), restricted the Owner role, and added a seamless Transfer Ownership capability.
Transformed member role selection in project team tables into an interactive nested submenu for a cleaner and more intuitive dropdown interface.
Redesigned the dashboard and project layouts with a full-height sidebar and streamlined project switcher.
Added multi-project support with GitHub/Vercel-style clean URLs (/[username]/[projectSlug]), unique username collection on signup, and a dedicated project sidebar.
Aligned the website's MCP server metadata and documentation with the standalone MCP service release.
Made vault rotations atomic, strengthened custom-key derivation, closed authentication enumeration, and limited anonymous CLI handshakes.
Aligned MCP handshake, health, and server-card version metadata with the package manifest.
Refined the security onboarding flows to seamlessly link passkeys, improved horizontal scrolling on API keys, and dynamically surfaced vault encryption state.
Hardened route guards and authentication boundaries, fixed Vault Key base64 encoding for Unicode compatibility, and adjusted CSP rules for optimal React execution.
Comprehensive polish of all authentication flows (login, registration, password reset, email verification): responsive flex layout, mobile numeric keypads for OTPs, standard autocomplete attributes, and unified branding.
Added secure, full-stack email verification and password reset workflows using cryptographically secure 6-digit OTP codes, SHA-256 hashed storage, rate-limiting, and branded transactional email templates.
Redesigned the landing page with an infinite ecosystem logo marquee, sleek frameless hero dashboard preview, and refined button proportions.
Replaced placeholder codeblocks with authentic high-resolution screenshots of the dashboard, CLI, and MCP. Optimized mobile grid spacing and responsive hero layouts.
Separated Google OAuth authentication flows to enforce explicit intent: preventing unintended account creations during sign-in when no profile exists, and blocking duplicate registrations when an account is already registered.
Added permanent account self-deletion in user settings with cascading purge of secrets, tokens, and passkeys, updated comprehensive Terms of Service and Privacy Policy, and standardized support channels on support@apivault.tech.

Integrated custom static OpenGraph preview assets across the web platform and aligned all ecosystem dependencies, Agent Skills, and documentation with the official production domains.
Updated default backend authorization server and public MCP resource endpoints to production domains (https://mcp.apivault.tech and https://apivault.tech).
Configured the CLI default API gateway to https://apivault.tech and updated standalone PowerShell and Bash installation script URLs.
Added production-grade SEO architecture including dynamic sitemap.xml, robots.txt crawl rules, edge-rendered OpenGraph & Twitter cards, Schema.org JSON-LD structured data, and canonical domain resolution for apivault.tech.
Updated the Two-Step Verification challenge screen to query and display only the specific authentication methods (Authenticator App TOTP, Passkey MFA, or both) configured and active on the user's account.
Polished the mobile navigation and settings layouts, added post-login origin deep-link preservation, and refined roadmap/changelog UI across touchscreens.
Standardized custom encryption terminology to Vault Key across all platforms, implemented accessible ConfirmModals, and introduced structured DocsStep walkthroughs in the documentation.
Separated the Model Context Protocol (MCP) server into an independent, public repository with zero database credentials and launched dedicated scope-enforced REST API gateway endpoints (/api/mcp/v1/keys).
Hardened OAuth 2.1 scope isolation across REST endpoints, added strict redirect URI validation in Dynamic Client Registration (RFC 7591), and added standard CORS preflights and RFC 6749 Cache-Control headers.
CLI update standardizing custom encryption prompts and flags to Vault Key, resolving package version dynamically from package.json, and preparing npm distribution.
Launched the public interactive Product Roadmap with deep-linking, multi-project capability teasers, and a unified detail modal.
Redesigned all notes, warnings, tips, info, and danger notices across documentation with modern callouts, harmonized color palettes, and variant-matched inline code badges.
Added an authenticated Live Mode toggle and clean monospace mode tabs to the in-browser terminal, allowing developers to execute real zero-knowledge CLI operations directly against their vault.
Introduced dedicated shareable detail pages for changelog releases with AI assistant integrations, real-time search, mobile filter selector, and edge-to-edge dashboard card polish.
Added a persistent floating action button (FAB) for the interactive shell with global keyboard shortcuts, active session radar beacon, and inline JSON copy buttons.
Built an emulated interactive documentation terminal runner supporting 100% Commander CLI parity, quote-aware tokenization, interactive prompt wizards, and autocompletion.
Added user profile avatar image rendering from database columns, quick navigation links in user dropdowns, and refined mobile drawer navigation with theme toggle.
A major redesign of the ApiVault documentation portal introducing a command-palette search modal (Cmd+K), responsive mobile navigation drawer, and step-by-step guides.
CLI update standardizing vault key flags to --vault-key for subcommand consistency and adding custom encryption support to keys modification.
Connect AI agents in Cursor and Claude Desktop directly to your ApiVault keys via Model Context Protocol (MCP) with OAuth 2.0 authorization.

Initial release of the apivault command-line client supporting secret process injection, dotenv export/restore, and local CLI configuration.
The initial release of ApiVault — zero-knowledge secret management built for developers, terminal workflows, and security-focused teams.