Planned

In Progress

Done

Main Roadmap

Available on: Enterprise onlyBlock license validation requests from specific countries - at the organization level or per individual product. Fits natively into KeyPort's existing 3-tier IP blacklist system as a geographic enforcement layer.What's included:<ul><li>Block any country from validating licenses across your entire org</li><li>Override at the product level - block specific countries for specific products only</li><li>Both org-level and product-level blocks can co-exist</li><li>Blocked requests return a clear <code>COUNTRY_BLOCKED</code> error response</li><li>All blocked attempts are logged in your audit trail</li><li>Manage via a simple country picker in your dashboard settings</li></ul>

Country Block

Darshak

Available on: All Plans A dedicated secret API key system so developers can manage their licenses entirely programmatically - no dashboard needed. Perfect for automating license creation when a customer completes a purchase on your own platform. What's included:<ul><li>Generate secret API keys from your org dashboard (shown once, like Stripe)</li><li>Create and manage license keys via API</li><li>Create and manage products via API</li><li>Update, revoke, suspend, and list licenses via API</li><li>Reset IP history, fetch your org's customer info, and list products - all via API</li><li>Scoped keys - each key can be set as read-only or full read + write access</li><li>Full audit trail - every management API action is logged </li></ul>Plan limits:<ul><li>Free - 1 key, read-only access</li><li>Pro - 2 keys, read-only or read + write (your choice per key)</li><li>Enterprise - Unlimited keys, full access</li></ul>

Management API

Available on: Pro + EnterpriseSee exactly where in the world your license validations are coming from, broken down by country and region.What's included:<ul><li>World heatmap showing validation traffic by country</li><li>Top countries list with call counts and percentage breakdown</li><li>Filter by product and date range</li><li>Data is tracked per validation call automatically - no setup needed</li><li>Free plan users see a locked preview to understand what they're missing</li></ul>

Geographic Analytics

What's included:<ul><li>TOTP - works with Google Authenticator, Authy, 1Password, any standard authenticator app</li><li>Passkey - biometric or hardware key login (Face ID, Touch ID, YubiKey)</li><li>10 one-time recovery codes generated on setup in case you lose your device</li><li>Email-based recovery fallback</li><li>Manage multiple passkeys per account, each named by device</li></ul>

2FA (TOTP) + Passkey

Ginga

Plan limits:Free :- system default Pro :- Up to 3 custom formats Enterprise :- Up to 6 custom formats What a dev can do:<ul><li>Define their own key patterns using a simple format (e.g. <code>STUDIO-XXXX-XXXX</code>, <code>PRO-XXXXXXXX-XX</code>, <code>APP-XXXX-XXXX-XXXX</code>)</li><li><code>X</code> = one random alphanumeric character, fixed text like <code>STUDIO-</code> stays as-is</li><li>Save multiple named formats per org ("Short Key", "Full Suite Key", "Beta Key")</li><li>Mark one as the org default</li></ul>On license creation flow:<ol><li>Format dropdown shows all saved formats for the org</li><li>Default format is auto-selected</li><li>A live preview shows what the generated key will look like - e.g. <code>STUDIO-A3X9-K2MN</code></li><li>Dev clicks Refresh to generate a fresh preview key</li><li>Dev can switch to a different format from the dropdown - preview updates instantly</li><li>On create, the actual key is generated using the selected format</li></ol>Settings page (Org Settings → Key Formats):<ul><li>Create / edit / delete formats</li><li>Name each format</li><li>Set one as default</li><li>Preview updates live as you type the pattern</li></ul>

Custom License Key Format - Full Detail

Available on: Pro + Enterprise Right now every license key is tied to a single product. If you sell a bundle of plugins or tools, you have to generate multiple separate keys and send them all to your customer - which is messy for you and confusing for them.License Groups / Bundles solves this by letting you group multiple products together and issue a single license key that validates across all products in that group. Example: You sell three plugins individually and also offer a "Full Suite" bundle. A customer who buys the bundle gets one key. That key validates successfully for any of the three products. A customer who only bought one plugin gets a regular single-product key as usual. What's included:<ul><li>Create named bundle groups inside your org (e.g. "Full Suite", "Starter Pack")</li><li>Assign any of your products to a bundle</li><li>Generate a bundle license key just like a regular license</li><li>Validation works exactly the same - dev calls validate with their key + product ID, no integration changes needed</li><li>Bundle licenses appear clearly labelled in your dashboard and customer portal</li><li>IP limits, expiry, and all existing license settings still apply to bundle keys</li></ul>

keyport

Main Roadmap