SignalrySignalry

API-first event record

Store the exact events
your systems emit.

Signalry is an API-first event ingestion and later querying/inspection platform. Send events via direct API requests, preserve raw JSON and timestamps immutably, and inspect what happened when you need the truth.

Raw JSON preservedTimestampedOrg-scopedNo inbound webhooks
Create accountLog in

Built for debugging, support investigations, and rollouts.

Designed for inspection, not analytics dashboards.

Scroll for the model: Send → Store → Inspect

Example shape
Illustrative payload and response. Not a finalized schema.

Request (example)

POST /v1/events
{
  "type": "user.signup",
  "occurredAt": "2024-08-10T14:32:11Z",
  "payload": {
    "userId": "user_123",
    "plan": "starter"
  }
}

Response (example)

{
  "id": "evt_64f3b7",
  "receivedAt": "2024-08-10T14:32:11Z"
}
Signalry stores the raw payload as sent, plus timestamps. Query and inspect later when you need to reconstruct what happened.

What it is / Why it exists

A stable event record for later investigation.

When an incident hits, a customer reports a problem, or a rollout behaves unexpectedly, you need the exact payload your backend emitted—without guesswork.

Signalry focuses on keeping the record clean: raw JSON payloads, timestamps, and an immutable history scoped to your organization.

Deliberate ingestion
Events are intentionally sent via API requests.
Immutable storage
A record you can reason from later.
Inspection-first
Built for tracing what happened, not summaries.
Org-scoped access
Multi-tenant by default; keep teams aligned.
Designed for engineering, product, and supportPreserves raw payloads and timestampsOptimized for querying and inspection

How it works

Send, store, inspect.

Signalry keeps the original event payload so you can trace what happened without reinterpreting data.

Create account
01Send
POST events from your services the moment they occur.
Keep your own shape; include what you need.
02Store
Immutable, timestamped records with raw JSON preserved.
A consistent history for the entire org.
03Inspect
Query later to reconstruct context with clarity.
Answer: what was sent, when, and by whom.

Use cases

Built for teams who need the facts.

The event record is built for investigation—when the details matter.

Debug an incident
Trace edge cases by inspecting the exact events your system produced during a failure window.
See raw payloads, not derived summaries.
Support investigation
Review the precise sequence around a reported issue and confirm what was emitted.
Reconstruct history from the record.
Verify a change
Confirm what actually emitted during a rollout, migration, or refactor—before and after.
Validate behavior with confidence.

Principles

Evidence over interpretation.

Keep the record stable so teams can reason from the same truth—even weeks later.

Raw JSON preserved
Timestamps preserved
Immutable event history
Org-scoped access
Query and inspect later

Start building on a clean event record.

Capture what your product emits today, and inspect it later with confidence.

Create accountLog in