Back to PermitCore

Changelog

What's new in PermitCore, newest first.

Total active device capacity

Plan limits now cover occupied device seats across all keys: Free 50, Starter 1,000, Professional 10,000 and Enterprise unlimited, plus active top-ups. Test, revoked, expired and imported seats count. Renewals and plan changes never reset usage. Above-cap accounts retain existing devices under normal license rules; only new activations return ActiveDeviceLimitReached. Confirmed device removal or key reset releases seats. Same-device node-locked reactivation reuses its seat.

Safer demo email and durable review-request limits

Demo and internal test tenants are excluded from scheduled campaigns and summaries. Central outbound checks block reserved/demo recipient domains before SMTP. Password reset, verification and OTP to real domains remain available. Customer-story requests use a durable once-per-account/email attempt marker instead of relying on expiring audit history.

Store setup checks and consistent guidance

Store Settings separates saved API verification, product mappings and notification history from the manual sandbox purchase check. App, Help Center and public documentation share one setup checklist. Dashboard documentation now follows the existing product → license → real validation onboarding. Bundle help describes one key with multiple product entitlements and account-only key access; recurring-license guidance follows the purchase's original provider.

Account-only license notifications

Purchase and trial emails link to the buyer’s Store account instead of containing a license key. This also covers historical guest purchases, legacy template variables and retries. Customers sign in and verify their purchase email to view retained keys. Order-status views no longer schedule removal of encrypted account delivery material.

Clearer key storage and access explanations

The homepage, pricing summary and Security storage table distinguish browser-passphrase protection for Admin-created keys from server-managed Store delivery and optional escrow. Validation receives submitted keys over HTTPS. Nearby links make security boundaries, current service status, data processing terms and export options easier to review before signing up. Key processing and SDK behavior are unchanged.

Dedicated startup licensing preview

The app-startup licensing guide now has its own social preview image, separate from its blog card illustration.

Earlier public-page font loading

Public pages request their Inter and Space Grotesk fonts early, keeping the existing typography and pricing controls. This reduces late font replacement during initial loading.

Clearer mobile navigation and Admin tables

On small screens, the menu scrolls above the cookie banner so Sign In and registration stay reachable. Pricing chips and comparison notes use readable text sizes. Disabled checkout actions look unavailable, and company activity tables follow the selected Admin theme.

Lemon Squeezy Store checkout

Each vendor can select Stripe, Paddle or Lemon Squeezy for new Store checkouts. Existing subscriptions keep their original provider. Lemon Squeezy uses dashboard-created variants; multi-product carts use one aggregate provider line and separate PermitCore purchase shares. A pending invoice or simulated success never extends a paid license without canonical payment evidence. Setup instructions are available in Store Settings, Help Center and the Store documentation.

Clearer account security, payment event recovery and documentation

Security table-of-contents links preserve same-page scrolling. Authenticator enrollment now shows a locally generated QR code with a manual-key fallback and a restart option for unfinished setup. Store payment settings include webhook URL copying and clearer missing-price diagnostics. Exhausted failed notifications can be archived with confirmation and reopened through Retry, retaining their history and payment records. Canonically verified zero-value Paddle transactions do not grant or renew licenses. Documentation PDFs include grouped chapter bookmarks, matching headings and a new page for each chapter. Customer device removal asks for confirmation, while recorded last-active times and a SuperAdmin company activity overview help explain account activity without exposing user browsing history.

Shared BLUE/GREEN preview and verified internal TLS

Hosted BLUE and GREEN share production account data, database, cache and authentication keys. Staging URLs preview the inactive application slot; authorized Nexova QA uses that shared data. Database/cache and application links keep verified TLS. Existing customer accounts, Store provider choices and SDK 2.1.1 behavior are unchanged.

Verified encrypted backup generations

New scheduled backups and deployment snapshots use isolated generations, streaming encryption, verified off-site copies and 30-day expiry eligibility. Legacy archives are retained separately. Holds and verification failures delay cleanup; the newest verified deployment recovery point stays until replaced. Restore discovery handles both legacy and new scheduled archives without overwriting a live database.

Verified organization SSO sessions

Required tenant SSO providers now govern password, global social sign-in and existing interactive sessions. A verified provider binding lets legitimate SSO sessions refresh; unbound older sessions need a fresh SSO sign-in. API keys and support impersonation retain separate rules. Existing organization settings are preserved.

SuperAdmin MFA enrollment rollout

A configurable fixed deadline supports 14 days for SuperAdmins to enroll an authenticator and save recovery codes. After enforcement starts, existing sessions and refresh credentials cannot bypass enrollment. Enabled authenticators cannot be replaced through setup alone; Settings installs new credentials after verification. Company MFA policy and license SDKs retain their behavior.

Auditable audit-retention batches

Audit cleanup saves each deleted batch and its count-only receipt atomically. Failed batches roll back and report incomplete work; earlier committed receipts remain. Tenant plan windows are unchanged. System audit cleanup has a separate operator switch, disabled by default, and ordinary application access still cannot delete audit rows.

Complete activation history minimization

The daily activation-retention job clears old country, city and end-user email even when the IP is already empty. Activation records, device binding, license material and usage counters are preserved. The existing retention window remains unchanged; retained metadata and backups have separate boundaries.

Clearer documentation PDF page breaks

PDF section openings reserve room for their heading and opening content. Long tables continue across pages, and the clickable table of contents follows the section. Use it rather than fixed page numbers as documentation changes.

1 November 2026

Private Certbot diagnostic file records

Normal Certbot diagnostic files omit message, private-key and exception payloads. Console output, command results and original rotation remain unchanged; existing records are retained. Custom entrypoints and direct streams remain separate. No certificate issuance or renewal acceptance is claimed.

Private NPM application logger arguments

NPM application loggers omit raw certificate/key objects, commands, initial-admin credentials and error payloads while keeping severity, scope and fixed operation names. Bootstrap login and command/certificate results keep their behavior. Direct process output, diagnostic files and stored history remain separate.

Private Public/Admin web-server errors

Both web servers send error events to the existing isolated collector using distinct fixed source labels. Raw URL/message payloads are discarded before storage, with the existing notice threshold and request, SPA, asset and security-header behavior preserved. Historical records and other logging layers remain separate.

Private gateway and outer proxy error output

Configured gateway/NPM error events discard raw URL/message payloads before storage and retain only fixed diagnostic categories and severity. Best-effort logging preserves customer request handling; existing history and other logging layers remain separate.

Bounded library diagnostic output

The supplied Console/File outputs omit raw selected library SQL/URI/exception data while retaining diagnostic codes. Requests and operational behavior remain unchanged. Existing log rotation was inventoried without changing retention or deleting history; custom sinks and edge error logs remain separate scopes.

Safe authentication errors and Store mail job references

Unauthorized exception responses omit raw provider text while keeping fixed application explanations. Store mail reference mode queues only an outbox ID and uses the original purchase snapshot, with a compatibility rollout for existing workers and queued jobs. Delivery templates, customer key protection and retry rules remain.

Private application and job failure diagnostics

Reviewed license/webhook, metering, analytics, expiry, retention and self-host job failure records use bounded diagnostics without raw exception payloads. Existing responses, retries, outage fallback and business decisions remain unchanged.

Safer startup failure diagnostics

Reviewed migration, bootstrap, installed-status and installation failure records omit raw exception payloads while retaining bounded code diagnostics. Existing continuation, installation responses and customer configuration remain unchanged; skipped tasks are not successful deployment.

Safe setup connection test errors

Database and SMTP tests omit raw provider exception text while preserving result statuses, missing-provider guidance and successful test sending. Existing transport settings, templates and installation behavior are unchanged.

Safe Stripe administration errors

Subscription sync and metered-price setup return operation messages instead of raw provider exceptions. Per-tenant sync failures, HTTP status, price-save behavior and successful reconciliation retain their existing rules.

Private webhook transport error fields

New webhook delivery errors and simulator transport failures omit raw exception text. Existing signing, HTTP status, receiver response previews and retry timing remain unchanged.

Safe self-host failure audit details

Self-host check-in failure audits omit raw exception messages and use an independent tenant-scoped save, preserving failed business writes and existing check-in responses. Audit storage remains best effort when the database is unavailable; historical records are unchanged.

Private administrative and operations failure records

Reviewed contact, mail-preview, GDPR, escrow, self-host and digest error events omit raw exception payloads while retaining bounded diagnostics. Existing failure responses, operation results, audit records and best-effort notification behavior are preserved.

Private billing and lifecycle failure diagnostics

Reviewed billing, price administration, Stripe webhook, dunning, expiry and trial-reminder error records use bounded diagnostics instead of raw provider/mail exceptions. Existing payment, refund, grace-period, webhook response and retry behavior is retained.

Private mail error records with delivery retries preserved

Verification, welcome, Store/Portal recovery, OTP and license-delivery failures omit raw mail payloads from their diagnostics. License-delivery jobs retain automatic retries using a safe failure record. Templates, intended emails, existing links and customer licenses keep their behavior.

Private authentication failure diagnostics

Reset-mail and tenant SSO exchange failures retain code/status metadata without raw exception payloads or reset URLs. Global API failures log route templates rather than bound private paths. Existing sign-in, reset links and generic error responses retain their behavior; other application and edge error logging remains a separate review scope.

Safer request access records and clearer SSO setup

Supplied API gateway, Public, Admin and configured outer NPM access formats omit request paths, query strings and Referer while retaining correlation and operational metadata. Error logs and external proxy records remain separate review scopes. Existing links keep working. SSO setup now marks the email domain required and points to Settings → SSO.

Safer sign-in transport and referrers

Tenant Google SSO profile requests now send the provider token in an Authorization header. Web referrers carry at most origin, protecting paths and queries even across SPA navigation; direct Admin login/reset/callback and Portal pages use no-referrer. UTM and current-page event values remain. SSO instructions clarify optional role-bound auto-provisioning and the password-form display preference. Existing links and sign-in settings keep their behavior.

Secure internal analytics preferences

Internal-browser and signed-in Admin telemetry flags now use Secure cookie prefixes on HTTPS. Existing exclusions are retained during upgrades, without changing login sessions or licensing. Reload saved tabs after updating. HTTP development does not create insecure fallback cookies.

Clearer rules for new account passwords

New passwords use 15-128 characters, allow spaces and Unicode without a required character-type mix, and are screened locally for common or obvious account/service values. Existing passwords keep working for sign-in without forced rotation. Registration, creation, invitation, change, reset and initial setup share the rules; the customer Portal reset link now shows its new-password form.

Password-change identity confirmation

Every user, including SuperAdmin, must confirm their current password to change it. SuperAdmin resets of another user require the acting administrator's password, have a distinct audit entry and invalidate the target's sessions. Self-changes keep the current session. Password changes require interactive authentication; license API keys and existing login passwords are unchanged.

Licensing rollout, packaged apps and customer recovery

New guides cover provider migration, Python desktop releases, license error UX and perpetual fallback planning. They explain existing controls and application responsibilities; no new importer, packager, updater or automatic fallback conversion is added.

Independent game sales and clear access promises

The new direct game-sales guide compares platform keys, download URLs and your own licensed build. It connects the current Unity/Store flow with delivery, offline and support boundaries. Store docs and Help link it.

31 October 2026

Current SDK application tutorials

The eight application and Store tutorials now use the SDK 2.1.1 setup: current Go module imports, updated Java/Unity versions and consistent Stripe/Paddle instructions. C++ and Python examples check both offline activation and later validation; offline setup and application host requirements are explicit. SDK behavior and packages are unchanged.

Signing-key rollout and recovery

The signing-key rotation guide distinguishes routine replacement, current-key compromise response, application trust updates and secure export. Business Continuity docs and Settings Help link it.

Licensing across virtual machines

The VM licensing guide covers cloned device identities, migration recovery, floating consumers and offline limits. Floating documentation and Licenses Help link the guide.

Clear team-seat policies

The new team license guide explains device and concurrent limits, fixed Store packs, customer device removal and the boundary between billing and existing-license updates. Activation-limit docs and Help link the guide.

License checks for paid MCP tools

A new MCP monetisation guide includes executed Node and Python policy helpers and explains client configuration, feature gates, protocol output, offline proof and hosted authentication boundaries. It adds no built-in MCP adapter or SDK behavior.

Paddle license delivery and renewals

A new payment lifecycle guide explains verified purchases, same-key renewals, grace, zero-value updates, refunds and webhook retries, alongside Stripe. The shared setup guide links it from Store settings, Help, public docs and PDF.

Security support and software licensing

A new CRA planning guide separates license duration, paid upgrades and security support, with official sources and clear product limits. It is not legal advice or a compliance attestation.

Clickable documentation PDFs

Exported documentation now has safe HTTPS and email links, plus a table of contents that jumps within the PDF. Tier-filtered exports only link to included sections.

CLI licensing guide for unattended jobs

A new CLI guide covers CI, Docker and SSH with executed Node, Python and Go examples, secret handling, exit codes and separate device/floating-seat policies. SDK behavior and versions are unchanged.

Explicit private API cache controls

Sign-in, authenticated API responses, API writes and authorization failures explicitly prohibit browser and proxy storage. Public catalog reads retain their short cache policy. Session deadlines, saved sign-in storage, checkout providers and SDK packages are unchanged.

30 October 2026

Reliable first startup with restricted database access

Automatic installation creates the initial administrator through a separate maintenance database connection. Normal requests retain their restricted role and tenant isolation. Existing administrators are preserved; bootstrap environment values do not reset installed accounts. SDK packages and payment-provider settings are unchanged.

Reuse unchanged frontend assets after updates

Public and Admin builds give scripts and styles content-derived addresses so repeat visits can reuse unchanged files. Ordinary mutable paths remain uncached; HTML, sign-in, private responses and configuration remain fresh. This does not change session deadlines, checkout providers or SDK packages.

Browser policy controls and accessible cookie preferences

Frontend images support HTTP Content Security Policy observation and enforcement with bounded, sanitized first-party diagnostics. Owned scripts and event handlers are externalized. Cookie preferences keep keyboard focus inside the dialog, dismiss unsaved changes with Escape or Close, and return focus to the opener. Public sign-in links resolve to the matching environment before interaction.

Platform billing sandbox preparation and portable history

Manage Subscription obtains a fresh Paddle portal session on each open, including providers' longer signed links.

SuperAdmins can prepare a separate Paddle sandbox connection with guided credential, webhook and catalog setup. Stripe stays the default for platform plans; existing subscriptions retain their provider. Account-data version3 includes platform Paddle checkout/event history. Recovery accepts older archives, closes historical payment work and clears operational billing bindings before reopening. Live platform Paddle is held; vendor Store Stripe/Paddle choices and SDK2.1.1 remain unchanged.

29 October 2026

Lighter first visits to licensing resources

Complete pre-rendered glossary, platform and alternatives pages use native navigation and FAQs without downloading the application runtime. Store, pricing, documentation and other interactive pages retain normal startup. Cookie controls, analytics isolation and sign-in destinations keep their existing rules.

Licensing definitions, platform guides and alternatives

New public guides explain device binding, activation and concurrent seats, outline integration boundaries for Electron, Python, npm, Tauri and WordPress, and compare migration questions for Keygen, Cryptolens from Devolens and LicenseSpring. Visible FAQs match structured data; competitor sources are linked. The guides add no new SDK or ready-made framework plugin.

Clearer Store discovery and initial page descriptions

Marketing Store links lead to the setup guide instead of a test tenant. Initial HTML descriptions distinguish browser-created keys from Store delivery, matching the full security guidance. The Store article reflects its actual revision date. A site ownership verification meta tag adds no directory badge or claim of external approval.

28 October 2026

Consistent account recovery packages

Verified CompanyAdmins can acknowledge and download a separate recovery ZIP containing a consistent account snapshot, available original Store license values and stored inline image bytes. The archive includes coverage, checksums and operator instructions; it is not encrypted. The recovery helper refuses existing accounts, verifies relationships and rehashes recovered values under the target's own keys. It preserves signing trust with the separate signing-key export and original browser passphrase. Missing historical values are reported, with an explicit incomplete-restore option that disables those licenses. Authentication, payment connections and operational jobs require review before reopening. External asset URLs remain references; SDK behavior and package versions are unchanged.

Accurate payment setup Help and working webhook copy

Help distinguishes platform Stripe billing from vendor Store checkout through Stripe or Paddle. The platform webhook Copy button copies the displayed URL and reports browser clipboard restrictions. Store visibility guidance requires Save Settings; listings with existing orders must be deactivated instead of deleted. Unavailable payment options have no public setup instructions or roadmap promise.

Stripe and Paddle launch scope

Store setup documentation describes the available Stripe and Paddle options. Each vendor selects one provider for the whole Store. Existing checkout behavior and payment connections are unchanged.

27 October 2026

Scoped status and security operations

The status page labels its database-connectivity scope and clears stale results after a failed refresh. Security guidance distinguishes scheduled GPG backups from compressed deployment copies, explains manual erasure/off-site retention and reports recovery-test limits. Vulnerability reports go to info@permitcore.dev; response times are handling targets. SDK packages and payment-provider settings are unchanged.

Modern TLS and transparent external checks

The hosted edge requires TLS 1.2+, retaining TLS 1.3. Dated SSL Labs and Mozilla Observatory results on the Security page describe host-specific checks rather than a certification. The API gateway root now returns public discovery links with security headers and no caching; it is separate from application health and the database-status probe. SDK behavior and package versions are unchanged.

Clear project identity and encryption boundaries

Project identity is permitcore, Zagreb, Croatia, with info@permitcore.dev as the main contact. Security, legal pages, marketing, blogs and Admin Help distinguish browser-created ciphertext from plaintext validation, server-managed Store delivery and optional escrow with privileged recovery. The Admin badge now says “Encrypted keys”. Account-export documentation and its manifest explain that Store order references are not decryptable key values; ordinary ZIP exports exclude delivery material and server secrets. Cryptographic behavior and SDK versions are unchanged.

Broader account-data portability

Account exports include customer profiles, Store catalog/design, orders, tax and provider receipts, subscription references, bundles/templates, metering, access configuration and historical public signing keys. Format version 2 lists all included files. Raw event payloads, authentication/provider secrets and uploaded file bytes stay outside the archive; asset URLs are references. The ZIP remains a selected, sequential export rather than a restorable database snapshot.

A practical exit plan and encrypted license exports

The exit plan explains offline deadlines, signing-key recovery, data export limits and planned-shutdown access. Account-data ZIPs now include encrypted license values, IVs, the tenant encryption salt, license controls and richer activation records. A versioned manifest records coverage and exclusions. Private signing keys and authentication/provider secrets remain outside this ZIP; it is not a complete service backup.

Practical key generation and connected documentation

A new key-generation guide provides executed C#, Python and Node.js examples and explains random identifiers, issued licenses and signed offline proof. Security documentation and Admin field help clarify the issuance boundary. Internal-link and raw social-preview checks cover the actual built pages. Hosted HSTS now uses one complete field; scoped edge gzip/identity rules cover the reported quality-zero request profiles while direct static Brotli through Cloudflare remains held.

Signing-key recovery on every plan

CompanyAdmins on every plan, including Free, can export their own signing keys and use the associated key lifecycle tools in Settings → Security → Business Continuity. Private key responses cannot be cached. Existing authorization, tenant isolation, encryption and audit records remain in place. Export supports your own tested recovery plan; existing token deadlines and separate offline-activation and self-hosting entitlements still apply.

Smaller WebAssembly transfers and prioritized Store highlights

Public and Admin nginx serve existing Brotli-compressed WebAssembly files on direct connections to compatible browsers, retaining gzip and uncompressed fallback. Cloudflare traffic keeps its existing gzip path while proxy negotiation is being verified. The first Store slide image gets eager/high-priority hints; later slides use lazy/low-priority hints. Vendor image URLs, carousel controls and autoplay remain the same. Browser startup CPU and vendor image sizes still affect loading time.

Consent Mode v2 with internal traffic exclusions

Eligible anonymous public pages use denied defaults for analytics and advertising storage. Limited cookieless measurements can reach Google before a choice or after rejection. Analytics cookies and custom signup/checkout events require acceptance; advertising stays denied. Internal, test and private contexts send no Google measurements. Cookie preferences, Privacy and Admin help explain the distinction.

Consistent public URLs and content dates

Known public pages redirect trailing-slash URLs to their canonical path while retaining query strings. Sitemap modification dates follow committed page content and article dates. The official Nexova demo Store is excluded from search indexing without changing other vendors' Stores. A compact documentation discovery file links to current references.

26 October 2026

Billing-backed public pricing and a calmer sign-in transition

Public pricing snapshots use a captured billing response instead of hardcoded prices and trial flags. Live pages refresh pricing and show an availability message when data cannot be loaded. Decimal prices are preserved and annual savings follow each plan's amounts. Sign-in waits for session initialization and uses a neutral layout during anonymous redirects, avoiding a brief Admin sidebar before Login.

Floating session authority and a tested integration guide

Heartbeat rechecks the current license and floating-plan entitlement. Denied renewal grants no new session proof. Checkout and renewal grants are bounded by the license access deadline, preserving applicable post-expiry and Store payment grace. The floating guide, reference and comparison article share an SDK-compiled lifecycle example that cancels cooperative work on renewal failure and awaits seat return. Admin help explains limits and confirmed cleanup.

Readable contact addresses and documentation examples

Generated page snapshots preserve contact links and email examples as written, including for crawlers and visitors without JavaScript. API and SDK help clarify which sample values you need to replace when integrating.

Clearer search and SDK reference descriptions

Public search and share previews use complete descriptions, shorter titles and current SDK installation requirements. Blog search summaries are separate from card excerpts. SDK Help reflects the published 2.1.1 release and its platform testing limits.

Confirmed checkout revenue in acquisition analytics

Eligible purchase events use the verified checkout's actual discounted net amount and currency, with tax and shipping separately. Trials, pending confirmations and unrelated subscription state cannot create paid revenue. Reloaded confirmations suppress duplicate events; consent and internal/test exclusions remain in force. Registration confirmation distinguishes paid checkout from trial activation. Pricing actions identify the clicked plan and location without changing the selected billing cycle.

A clearer Free-plan offer and easier mobile controls

Billing Help distinguishes your PermitCore subscription from customer payments through your Store's selected Stripe or Paddle account.

The homepage primary action starts the Free plan with no card or time limit. Three-month trial offers stay beside eligible paid plans and on Pricing. Registration explains the distinction. Mobile payment-period controls, SDK links and Store buttons have larger touch targets; Store slide controls have descriptive names and room around the purchase link. Versioned stylesheet URLs deliver the updated layout to returning visitors.

SDK 2.1.1 across all eight languages

.NET, Node.js, Python, Java, C++, PHP, Go and Unity share floating sessions, confirmed checkin, device-removal wrappers, boolean usage reporting and bounded transport defaults. Requests use ten-second attempts with two safe network/5xx retries; mutating operations are sent once. Redirects, HTTP rejections and malformed successful evidence cannot authorize from cache. See the SDK references and installation commands.

Configured trust for offline licensing

SDK 2 requires independently configured tenant public keys, retains the original signed proof and re-verifies its deadline and license/product/device context on every read. Legacy caches are ignored; manual offline activation uses a configured client instance. Go uses the /v2 module path. Anonymous online token-status checks work under tenant row-level security and preserve vendor self-issued tokens. Follow the offline migration guide when upgrading from 1.x.

Consistent installation and printable documentation

Installation examples use 2.1.1 throughout. The PDF retains SDK capability and request-configuration tables and omits decorative icons that cannot be printed reliably. PHP public result types autoload independently of client construction. Public docs, Admin SDK help and the related offline/Go/Unity articles describe the same behavior. Unity testing covers the portable core; Editor, IL2CPP and actual WebGL projects require target-specific checks.

24 October 2026

Clearer payment settings and setup help

Store Settings labels the saved active provider and mode, with explicit Stripe key mismatch guidance. Payment events expand to show safe identifiers and processing details, with labelled cards on phones. Paddle field help points to the matching credential settings; Help Center supports Escape and its walkthrough fills the article column. PDF disclosure titles retain heading styling. Keyboard activity is recorded even when a help popup consumes Escape.

Paddle credit-only subscription updates

Paddle completed subscription updates that only generate account credit (or have zero totals) are ignored after canonical API validation. They do not issue licenses, extend paid-through dates, send license emails or clear payment debt. Real paid renewals still require independent payment evidence.

Independent QA improvements

Mobile consent leaves sign-in reachable, utility pages describe themselves in structured data, and unknown Store landing URLs receive a real 404 when the configured gateway confirms they do not exist. Direct index.html requests redirect home. Field help has specific accessible labels; Admin map assets are self-hosted. SDK packages and live payment settings are unchanged.

Directory link update

LaunchNest was removed following QA on 27 October. The ToolFame badge remains in the shared prerendered footer. Install examples preserve literal package scopes and version suffixes, including copied commands.

Internal traffic exclusion for website analytics

Private Admin areas, staff/test traffic and nonproduction hosts are excluded from Google website analytics. An internal-browser preference works across PermitCore subdomains, while eligible anonymous registration conversions retain consent-based collection. Server activation reporting skips internal tenants and missing consent IDs. Activation signals originate only from production, and an analytics outage does not fail otherwise successful license checks. See analytics preferences.

Admin inactivity countdown and session recovery

Admin sessions use a server-enforced 30-minute inactivity timeout with a countdown during the last five minutes. Continue session, real input, navigation and reload keep an active session going; background requests do not. Expiry returns to Sign In with a clear explanation. Short-lived access tokens renew independently. Concurrent sign-ins preserve the successful session and show retry guidance for the losing attempt. See Admin session help.

23 October 2026

Vendor Store payment providers

Each vendor selects Stripe or Paddle for the whole Store. New checkouts follow that selection; existing purchases and subscriptions keep their original provider. Paddle supports catalog sync, itemized checkout, subscription renewals, payment recovery, refunds and provider documents. Payment settings start with provider selection and separate Account, Products & prices, Payment events and Store settings, with help beside the fields. See the Store provider setup guide.

20 October 2026

Software ownership and end-of-life planning guide

The Owned, Not Rented guide explains clear license terms, the limits of signed offline tokens, device moves and an end-of-life release plan. The security documentation and related offline/transfer articles describe the same continuity boundaries.

20 October 2026

Directory links in the public footer

The public footer includes Findly.tools and Turbo0 badges alongside the existing directory links. These links are also included in the static HTML served to crawlers.

19 October 2026

Store tax calculation and invoice history

Choose Vendor rates, Stripe Tax, or Managed Payments for eligible Stripe accounts and products. Stripe Checkout shows final tax before payment, and product settings select inclusive/exclusive pricing and a tax classification. Orders retain provider tax figures and Stripe invoice history across renewals. Existing stores keep their selected manual rates; provider setup must be ready before checkout. See Store tax setup.

19 October 2026

Store subscription renewals and payment grace

Paid Stripe renewals extend the same license through the paid billing period. Store settings provide a configurable 14-day default payment grace; apps receive payment state alongside grace metadata. Signed offline deadlines honor paid-through plus grace, and duplicate or reordered webhook deliveries preserve the subscription's entitlement. See Store setup and license controls.

June 2026

v0.9 — SSO, Resellers & Public Storefront Redesign

  • New Per-tenant SSO — OAuth 2.0 (Google, Microsoft, GitHub) and SAML 2.0
  • New Reseller system — resellers can sell license packs with margin tracking
  • New Metered billing — usage-based activation pricing via Stripe meters
  • New License bundles — sell multiple licenses as a single purchase
  • Improved Complete public storefront redesign with zero-knowledge showcase, interactive feature modals, trust signals section
  • Improved Full legal pages: Terms, Privacy, DPA, Security, Cookies
  • Fix Domain migrated to permitcore.dev
  • Security All 17 security audit findings resolved (JWT expiry, auth headers, CORS, rate limiting)

May 2026

v0.8 — License Store, Stripe & Analytics

  • New White-label License Store with Stripe checkout — sell directly to your customers
  • New Store customer portal — customers can view and manage their own licenses
  • New Stripe billing integration — subscription management, plan upgrades, invoices
  • New Analytics dashboard — activation heatmap, geographic breakdown, daily/weekly trends
  • New Webhook system — send real-time events to your endpoints, signed with HMAC-SHA256
  • New Custom license fields — attach arbitrary key-value metadata to any license
  • New Geographic restrictions — restrict license activation to specified countries
  • New Device fingerprinting — tie activations to specific machines
  • Improved Billing tier enforcement via activation pool (MaxTotalActivations)

April 2026

v0.7 — Offline Activation & MFA

  • New Offline activation — ECDSA P-256 signed tokens for air-gapped environments
  • New TOTP multi-factor authentication for all admin accounts
  • New MFA backup codes with secure one-time use
  • New GDPR tools — full data export (Art. 15/20) from admin settings; account deletion (Art. 17) handled on request
  • Improved Audit log now records IP address, user agent, and field-level diffs for updates

March 2026

v0.6 — Zero-Knowledge Encryption & Public API

  • New AES-256-GCM client-side encryption — plaintext keys are never stored
  • New PBKDF2 key derivation with 600,000 iterations and per-tenant salt
  • New Public validation API — POST /api/v1/validate
  • New Public activation API — POST /api/v1/activate with atomic counter enforcement
  • New HMAC-SHA256 lookup hashing — the stored value can't be used to verify key guesses without the server's secret
  • New Rate limiting — per-IP (60 req/min on public API) and per-tenant billing tier limits

February 2026

v0.5 — Core Platform Launch

  • New Multi-tenant architecture — full data isolation between companies
  • New Argon2id password hashing with per-user salt
  • New JWT authentication with role-based access control (SuperAdmin, CompanyAdmin, CompanyUser)
  • New Product and license key management
  • New Billing tiers: Free, Starter, Professional, Enterprise
  • New Installation wizard — one-command Docker deploy
  • New Blazor WebAssembly admin panel