What unkeyed/unkey shipped

This week: request body caps and streaming on Frontline, build pulls denied from the build registry host, redacted cookies and proxy credentials in gateway logs, per-root-key IP allowlists, order-fixed root key locks, case-insensitive bearer auth, and /openapi.json.

What shipped this week: Frontline now caps request bodies at 4MiB with a per-pod memory budget and streams bodies on the plain-HTTP listener. Builds deny pulls from the build registry host, so one project's Dockerfile can't pull another's image with shared credentials. Gateway logs redact Cookie, Set-Cookie and Proxy-Authorization values. Root keys support their own IP allowlists and show enabled, disabled and expired status. Root key mutation locks are ordered to prevent deadlocks, bearer auth parsing is case-insensitive, non-live production deployments can be stopped, and the OpenAPI spec is served as JSON at /openapi.json.

This week in Unkey: unkey login and workspace switch in the CLI, dashboard pages to approve CLI logins and manage sessions, a new logs.getApiRequestMetrics endpoint, the logs table on the SDK, a deterministic S3-FIFO cache, and keyspace IP allowlists now enforced.

This week in Unkey: the CLI now supports unkey login, unkey logout, and workspace list and switch, paired with dashboard pages to approve CLI logins and manage sessions. Large keychain sessions on macOS are stored without truncating. On the API side, logs.getApiRequestMetrics was added with denser buckets and the same filters as the log list, and the dashboard logs table and live mode moved to the SDK. The cache was replaced with a deterministic S3-FIFO store, an in-memory global rate limiter was added, keyspace IP allowlists are enforced in frontline, and rerolling a key now evicts cached verification. Deployments also return issues describing what is wrong with a running app.

This week: Unkey is now licensed under FSL-1.1-ALv2, with rbac and error internals kept under MIT. Krane runs workloads as Deployments behind a rollout gate. Rolled-back apps keep their live route. Timing headers are opt-in via X-Unkey-Debug. Frontline returns 422 for missing rat

This week in Unkey: the main license is now FSL-1.1-ALv2, with the rbac and error internals kept under MIT and icons under their package license. Krane runs workloads as Deployments behind a rollout gate, and Ctrl no longer moves the live route to a new deploy on a rolled-back app. The X-Unkey-Timing headers are off by default and can be turned on per request with X-Unkey-Debug=1, and frontline returns 422 instead of a 5xx when a rate limit named in a key auth policy does not exist. The dashboard new-app wizard is replaced by a guided card flow, and Safari log tables show rows again.

This week: deployments API gained branch and time filters plus more response fields. Dashboard usage, deployments, limits and permissions now read and write through the SDK. Krane spreads replicas across nodes. Dashboard requests are no longer logged when they come from the dashb

This week we moved several dashboard surfaces onto the public API through the SDK. Usage reads workspace.getUsage, limits read workspace.getLimits, deployments read listDeployments, and permission edits use permissions.updatePermission and permissions.updateRole. The deployments API also accepts branch and time filters, returns more of the fields the table shows, and orders by createdAt so later pages load faster. On the infrastructure side, krane now caps replicas per node and requires hostname spread for multi-replica deployments. We also stopped logging dashboard requests that come through the dashboard client, and fixed focus handling in the dashboard time range picker.

Shipped: root key v2 API with URN validation, portal session revocation from dashboard, Remote IP policy conditions, regional read replicas, and better UX for long-running operations.

This week's updates focus on production readiness and operational control. The new /v2/rootKeys.createKey API validates permissions server-side while the dashboard builder creates keys with URN-based policies. You can now revoke individual portal sessions without affecting the whole portal. Remote IP conditions let policies match client IP ranges, and the dashboard uses PlanetScale read replicas across regions for faster loads. Long-running worker steps now show progress immediately instead of a blank screen.

Shipped: Go 1.27.1 upgrade, API 1.1.46 with expanded URN permissions, dashboard SDK migration for keyspaces & overrides, app card redesign with search, and krane outage recovery.

This week we upgraded to Go 1.27.1, released API 1.1.46 with URN permission coverage across more endpoints, and continued migrating the dashboard from tRPC to SDK calls. We redesigned app cards with search functionality, added outage recovery for krane, and improved tooltip consistency across the UI. URN permissions now cover projects, apps, deployments, and more.

Frontline 1.0.26-rc.1 shipped. Better deployment visibility, safer key deletion, analytics scope back in the portal, and gateway policy fixes.

This week's updates focus on platform stability and usability. Frontline 1.0.26-rc.1 brings gateway policy fixes, project cards now show deployment status directly, and we added safeguards that warn before deleting recently-used keys. The portal re-implements analytics scope end-to-end, and we optimized dashboard performance by serving cached compute meter data. Removed all custom WorkOS code in favor of their hosted solution.