[RELIABILITY / STATUS]
Operational claims should have evidence behind them.
This page states what PaperJSX can verify publicly today. It does not present a synthetic uptime percentage or imply that local package availability is the same as hosted service availability.
REVIEWED 28 JUL 2026NO INVENTED UPTIMESOC 2 IN PROGRESS
Current public status boundary.
No automated public incident feed is connected to this page yet. For a suspected hosted incident, contact support@paperjsx.com. This is a disclosure of the current reporting limit, not an all-systems-operational claim.
| Surface | Availability model | Public evidence |
|---|---|---|
| Local packages | Run in the customer-controlled Node.js runtime; npm installation availability is external to a hosted PaperJSX SLA. | Versioned package tests and checked-in artifacts. |
| Local MCP | Runs over stdio in the customer-controlled environment. | Package documentation and local evaluation. |
| Hosted Platform | Authenticated PaperJSX-managed delivery. | Health endpoint and workspace delivery/audit evidence; no historical public uptime series is published yet. |
Reliability evidence we do publish.
- Native artifacts, source payload hashes, engine package versions, and structural-validation status in the sample manifest.
- Known quality gaps and the current blinded baseline on the evidence page.
- Security and delivery-boundary documentation on the security page.
Compliance and procurement.
SOC 2 work is in progress. PaperJSX is not representing itself as SOC 2 certified. Enterprise evaluations can request the current security materials, subprocessors, DPA, control status, and an honest gap list.
Support response targets, uptime commitments, data residency, and other negotiated controls apply only when they appear in an executed agreement. Public marketing copy is not an SLA.