back to atlas

ks · partner

industry · scale-tech4 partners · live

Partner.

Joint deliveries with infrastructure, platform, and rail partners. The contract is with the protocol — not the vendor.

Open a conversation Investor portal

how it works

From intro to renewal.

  1. § 0130 min

    Intro

    30-minute call to scope fit. We share the protocol roadmap; you share the integration shape and traffic profile.

  2. § 024–6 weeks

    Integrate

    Pre-release SDKs, joint architecture review, and a staging tier on the SSL. Maintainers sit in your standups.

  3. § 03rolling

    Production

    SLA on. Status pages cross-link. Quarterly reviews against shared metrics — DID resolutions, settlements, cache hit rates.

  4. § 04yearly

    Renew

    Annual roadmap alignment. Co-marketing on releases. Senior partners get a vote on breaking changes.

what partners get

Production-grade by default.

  • Pre-release SDKs

    Builds two semvers ahead of public. Catch breaking changes before they break you.

  • Roadmap input

    Quarterly working-group sessions where partners propose protocol amendments and vote on priorities.

  • Production SLA

    99.95% on the resolver and trade router. Status page parity, joint incident response.

  • Co-marketing

    Joint releases, conference talks, and case studies. We ship your logo on the foundry; you ship ours on the integration.

active partners

Who's plugged in.

  • Mux

    live

    Video pipeline for Indusland Inspire — DID-bound watch sessions and signal ingest for Oreoasis recommendations.

    infrastructure · neuronsite

  • Vercel

    live

    Edge deploy for the foundry and Indusland. did:ks resolver runs on Vercel's edge runtime.

    platform · identitysite

  • Stripe

    rolling

    Settlement rail for Duedale escrow. Stripe handles fiat in/out; the chain handles trust.

  • Clerk

    scoping

    Identity bridge — Clerk sessions resolve to did:ks documents, then back. Co-spec'd PDS handoff.

    platform · identitysite

shipped together

Integrations in production.

  • Indusland live with Mux

    Indusland Inspire ships short-form video on Mux's pipeline; viewer DIDs feed into Oreoasis retrievers without leaving the user's PDS.

    w/ Mux

  • Duedale escrow on Stripe rails

    Fiat settlement after on-chain trust resolution. Disputes route to attestor weight first; Stripe handles the bank rails second.

    w/ Stripe

  • did:ks resolver on Vercel edge

    Reference resolver deployed to Vercel's edge runtime — sub-50ms p50 globally, with PDS routing handled at the edge.

    w/ Vercel

asked often

Quick answers.

  • Do I have to migrate my stack?

    No. Partnerships are integrations, not migrations. The foundry runs alongside whatever you already ship.

  • What's the SLA?

    99.95% on the DID resolver and trade router. Joint incident response with status-page parity.

  • Can I sublicense the SDK?

    Yes, under the same Apache-2.0 / MIT licenses the SSL ships under. White-label is a separate conversation.

  • How do partners influence the protocol?

    Quarterly working-group sessions. Senior partners get a vote on breaking-change RFCs.