← Back to home
Comparison · Infra & APIs

Okta vs Depot

Side-by-side trajectory, velocity, and editorial themes.

Okta logo
Okta
INFRA · APISDEVOPS
1.3

Okta's developer push is concentrated on Cross App Access and ISV-friendly low-code integrations.

◆ Current state

The Okta developer surface is dominated by Cross App Access (XAA) content — protocol tutorials, an xaa.dev playground, and app-to-app connection guides — plus a recent OIN feature for ISVs called API Integration Actions and earlier work on entitlements. Cadence is roughly monthly. All recent posts are educational rather than product launches.

◆ Where it's heading

XAA is the centerpiece of the developer story. Okta is using the blog to seed an ecosystem around the spec while deepening ISV integration paths through Workflows-based low-code. An earlier MCP server hints at AI-agent identity interest, but the visible momentum is on XAA and OIN extensibility.

◆ Prediction

Expect more XAA enablement (partner-app tutorials, possibly a public-preview or GA milestone) and additional OIN features that push provisioning and entitlements toward AI-agent and ISV-tooling use cases.

D
Depot
INFRA · APIS
6.3

Depot is rounding out Depot CI into a credible GitHub Actions alternative, and just shipped nested virtualization.

◆ Current state

Eight of the last ten changelog entries are Depot CI updates: a new workflow summary page, environment-aware secret and variable variants, CLI commands for metrics, JSON status output, live log streaming, workflow listing and inspection, run cancel/rerun/retry/dispatch, and a DEPOT_JOB_URL env var in every job. Registry got pull-through cache improvements with provider presets. The dominant theme is filling in the feature surface a serious CI platform needs.

◆ Where it's heading

Depot is methodically closing the gap between its CI product and the incumbents. The recent run reads like a checklist: workflow UX, secrets, metrics, log streaming, scriptable CLI surface — the table-stakes ergonomics teams expect before migrating off GitHub Actions or CircleCI. The May 20 nested virtualization release expands what kinds of workloads Depot CI can host at all, not just how nicely it hosts them, which is a different and more aggressive move.

◆ Prediction

Expect more workload-expansion moves following the nested virtualization release — likely Android-specific tooling, deeper matrix/sharding UX (the workflow page already groups matrix failures), and continued CLI parity work. The secrets-and-variables variant model looks set up to grow into broader policy-as-code for CI configuration.

See more alternatives to Okta
See more alternatives to Depot