STI-PA Approved Certificate Authority

STIR/SHAKEN certificates,
issued the same day.

Request, renew, and revoke certificates for every OCN you operate — from an approved STI-CA, at flat, transparent pricing.

Pricing
$500/yr flat
Automation
REST + ACME
Certificates
Unlimited per OCN
POST /api/v1/certificates
curl -X POST .../api/v1/certificates \
  -H "Authorization: Bearer ..." \
  -H "Content-Type: application/json" \
  -d '{
    "ocn": "999Z",
    "validityPeriod": "1_year"
  }'

{
  "data": {
    "certificateSerial": "7f3a9c2e1b...",
    "status": "active",
    "ocn": "999Z",
    "expirationDate": "2027-11-16"
  }
}

Compliance, simplicity, security, and cost

A STIR/SHAKEN program is a compliance obligation first. Everything else follows from getting that part right.

  1. 01

    Compliance

    Every certificate meets the STI-GA SHAKEN Certificate Policy, RFC 8226, and RFC 5280 — issued by an approved STI-CA, not a self-signed workaround.

  2. 02

    Simplicity

    No manual tracking — automated renewal, expiration alerts, and STI-PA trust-list refresh, with certificates served from a global CDN for fast, reliable delivery.

  3. 03

    Security

    Security was the primary design goal, not an afterthought — signing material stays encrypted at rest, and revocation is deliberate and irreversible.

  4. 04

    Cost

    Flat, transparent per-OCN pricing with unlimited certificates included — built for small and mid-size providers that need to meet compliance without breaking the bank.

A platform, not just a dashboard

Certificate management designed to integrate with how your systems already work.

Full certificate lifecycle

Request, renew, deactivate, or revoke in a few clicks. Revoking always requires a typed confirmation.

Multi-OCN support

Manage certificates across every OCN, SPID, or RespOrg you operate — one dashboard for your entire portfolio, built for carrier groups, resellers, and MSPs managing multiple clients.

REST API and ACME

Request and renew certificates from your own systems, or point any ACME-capable client at our directory.

Need more than certificates?

Hosted Call Signing, DNO filtering, and TN Reputation round out the rest of your call-authentication stack, run for you.

Requesting a certificate shouldn’t be a project

Give us an OCN and a term and the certificate is issued instantly — no CSR to generate, no manual signing request to assemble. The paperwork happens once, during onboarding, not on every request, whether you’re in the dashboard, calling the API, or using ACME.

See the full compliance checklist →
Request a certificate
POST /certificates
{ "ocn": "999Z", "validityPeriod": "1_year" }

→ { "data": {
    "certificateSerial": "7f3a9c2e1b...",
    "status": "active",
    "expirationDate": "2027-11-16"
  } }

Ready to get your voice traffic signed?

Create your account and request your first certificate today.