Repository navigation
Price Sign: $0.50 per completed request, 5 a month on Free - #342
Merged
Merged
Conversation
- Rate: sign.completed_requests at $0.50 on the November 2026 card (Sign was switched on in production on 2026-11-06; nothing completed before). A seal is one SSL.com eSigner signing, about $0.19-0.25 at our tier. - Free includes 5 a month, enforced like other capped meters: a live request reserves one when it is sent (create with send, or send), and canceling a sent request releases it to the period it was sent in. SignService gains send/cancel bound to the usage gate; the API and the dashboard use them. - Sandbox requests are sealed with a self-signed test seal (sealerFromEnv's sandboxSealer), so tests never spend the CA's signings. - Docs: Sign's pricing section, the sandbox test seal, Going live. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
sign.completed_requestscosts $0.50, on the November 2026 card. Sign was switched on in production on 2026-11-06 (Switch Sign on in production, sealed by SSL.com eSealing #341), and no organization had completed a request there before. Our cost is one SSL.com eSigner signing per seal: about $0.19–0.25 at the 1,000-a-month tier, $1 at the smallest. Competitors charge $0.75 (BoldSign) to about $1.20 (DocuSign) per envelope.UsageGate:createwithsend, orsend), in the same transaction;SignServicegainssendandcancelbound to the gate, and the API (POST /v1/sign/requests/{id}/send|cancel) and the dashboard's cancel use them.sealerFromEnvalso returns asandboxSealer, a self-signed test seal, and completion uses it for sandbox requests. Before this, sandbox tests spent paid SSL.com signings.packages/sign/AGENTS.mddescribes billing and finishes Going live, including the eSigner trial ending on 2026-12-06.Testing
packages/sign/test/ship.test.ts):usage_limit_exceeded);turbo run typecheck test --affectedpasses 44 of 45 tasks. The one failure is@coss/risk's domain-age test, which fails only locally because of a stale cache row in the shared test database; it doesn't fail in CI.Review
Codex round 1: no findings.
🤖 Generated with Claude Code
Open in [code]smith · Need help on this PR? Tag
@codesmith-botwith what you need.