Skip to content
WickArc

WickArc / Trust center

Trust should be inspectable.

A live view of the core production request path, paired with precise boundaries around what WickArc verifies, protects, and does not claim.

LIVE CORE STATUS

Checking live systems

Running a fresh, uncached readiness probe.

Web application

This page and the public edge

Checking

Research API

Core application request path

Checking

Primary data store

Direct dependency probe

Checking

Queue and cache

Direct dependency probe

Checking

No verified receipt is available yet.

Point-in-time probe · no uptime percentage implied · response is not cached

Evidence, not a decorative green light.

The status above runs an uncached server-side readiness check. A successful receipt requires the research API to answer its exact contract and directly verify both PostgreSQL and Redis. A separate production monitor repeats the complete public gate every 15 minutes. Failure remains visible as degraded or unverified.

01 / FAIL CLOSED

Unknown is not operational

Timeouts, malformed responses, and unreachable dependencies never become a green status. The public result exposes only allowlisted states, not infrastructure addresses or credentials.

02 / FRESH RECEIPT

No cached reassurance

Each check bypasses caches, includes an observation time, and can be rerun manually. It is a current snapshot—not a historical uptime percentage or service-level promise.

03 / READ ONLY

Safe to verify

The public probe reads process and dependency health only. It does not access customer research, place orders, run models, send email, or mutate production records.

The boundary is part of the proof.

WickArc separates customer-visible assurances from controls that still require operator or independent evidence. This page deliberately avoids certification language and invented incident history.

Implemented and production-evidenced

  • Server-enforced authentication and workspace authorization
  • Private model artifacts, credentials, and sealed results excluded from public responses
  • Synthetic public demo isolated from customer records and brokerage action
  • Strict transport, framing, content-type, referrer, and browser-permission headers
  • Automated build, type, lint, security, dependency, and read-only release checks
  • Separate 15-minute production edge monitoring with exact contract checks
  • Point-in-time recovery with an isolated production restore drill completed October 10, 2026

Not asserted by this page

  • Guaranteed uptime or complete third-party provider availability
  • SOC 2, penetration-test, or regulatory certification
  • Successful email, billing, market-data, or long-running worker delivery
  • A customer-impacting failover or production rollback exercise
  • Research accuracy, profitability, or future investment performance

The live status covers the web application’s core API request path and direct PostgreSQL/Redis connectivity only. It intentionally does not convert a point-in-time response into historical availability or operational certification.