Free: 100 anchors a month, live now.

Free anchoring is live. Paid tiers are planned — design partners onboard directly today.

Things people ask before they reach out.

What counts as one anchor?

One POST /api/v1/anchors that successfully broadcasts. A manifest-backed proof counts as one anchor regardless of leaf count (10,000 items in a single transaction is still one anchor). Failed broadcasts — CSRF reject, validation error, broadcaster failure — do not count.

How do I estimate my monthly anchors and model cost at volume?

Anchors — not API calls or bound items — are the billed unit, so size your month in anchors first. A strong-timing agent session burns N + 2 anchors (one policy snapshot, one per decision, one manifest at close); batch mode burns 2 regardless of N. A single manifest binds up to 10,000 items as one anchor, so a high-volume event stream collapses to roughly items ÷ 10,000 anchors. Run your monthly volume through whichever shape you’ll use to get a monthly anchor count. Above the 100,000-anchor Pro cap the Scale plan is priced per anchor, quoted on that volume — email hello@satsignal.cloud with your estimated monthly anchors for a unit price.

Do all plans include every proof type?

Yes. The free plan and the planned paid tiers all support both privacy modes — Standard (proof details are public and hash-discoverable) and Sealed (proof details stay private; stored Mirror by default, or Blind if you withhold the salt). Either one can anchor a single hash or a manifest-backed proof (one Merkle root over many items, with selective disclosure per item) — manifest is the evidence shape, not a third privacy mode. Plans differ only in monthly anchor volume and the team/API features listed on each card.

What happens if I hit the free plan’s monthly cap?

The next anchor returns HTTP 429 with X-RateLimit-* headers naming when your window resets (start of the next calendar month UTC). Already-anchored proofs keep verifying; only new anchors are paused. If you need more headroom now, email hello@satsignal.cloud and we’ll lift the cap directly.

When will paid tiers open for self-serve checkout?

No public date yet. We’re onboarding design partners directly first, so billing, invoicing, and retention clauses get exercised against real customers before the self-serve flow goes live. Published Starter and Pro prices are the planned numbers, not currently live in checkout.

How do I get a paid tier or design-partner slot today?

Email hello@satsignal.cloud with your expected anchor volume, what you’re building (infrastructure, agent runtime, legal/provenance pipeline, etc.), and whether you need invoice billing or a custom retention window. Scale-plan invoices are billed directly by Satsignal in USD.

Do you accept BSV or other crypto for payment?

Not today. The chain is a settlement layer for the proofs; the billing relationship is a normal SaaS arrangement.

Is there a DPA? Can we embed or resell anchoring?

Both exist as complete published drafts, clearly marked pending counsel review: the data-processing addendum (draft) covers roles, the exact data inventory, per-mode retention, and subprocessors; the embedding & resale rider (draft) covers offering anchoring inside your own product (paying customers only, Sealed mode by default). Procurement teams that need a signed version now: email hello@satsignal.cloud.