How VelosCore delivers every event

Your service sends an event once. VelosCore fans it out to each subscribed endpoint, signs each request, records every attempt and keeps retrying until the endpoint answers with a 2xx or the schedule runs out.

Retries with backoff

A delivery fails on any non-2xx status or no response within 15 seconds. Each failed event follows this schedule, about 27 hours in total. Retries are never billed.

Attempt 1Immediately
Attempt 25 seconds
Attempt 35 minutes
Attempt 430 minutes
Attempt 52 hours
Attempt 65 hours
Attempt 710 hours
Attempt 810 hours

Delivery attempts for one invoice.paid message

V VelosCore

Messages
Endpoints
Event types
Settings

msg_2nX9fK · invoice.paid

ep_acme-erp

Attempt	Status	Latency
#1 Oct 27, 14:02:11 UTC	503	412 ms
#2 Oct 27, 14:02:16 UTC	Timeout	15,000 ms
#3 Oct 27, 14:07:16 UTC	200 OK	131 ms

Illustrative product interface

Signatures your customers can check

Every request follows the Standard Webhooks spec: webhook-id, webhook-timestamp and webhook-signature headers, with an HMAC-SHA256 signature over the ID, timestamp and raw body. Receivers reject timestamps older than 5 minutes to block replay attacks.

Rotate an endpoint secret at any time. For 24 hours both the old and new secret are sent in the signature header, so customers can switch without dropping events.

receiver.ts (your customer's server)

import { Webhook } from "@veloscore/node";

const wh = new Webhook(process.env.VELOSCORE_ENDPOINT_SECRET);

app.post("/webhooks", express.raw({ type: "application/json" }), (req, res) => {
  try {
    // Checks webhook-id, webhook-timestamp and webhook-signature
    const event = wh.verify(req.body, req.headers);
    handle(event);
    res.sendStatus(204);
  } catch {
    res.sendStatus(400);
  }
});

A portal your customers manage themselves

Embed the consumer portal in your dashboard with a short-lived link. Customers add endpoints, choose event types, see delivery logs and resend failed events without opening a support ticket.

portal.veloscore.online/app_2Hq81

W Webhooks

Endpoints
Event catalog
Logs

Endpoints

2 active

Endpoint	Events	Status
https://erp.example.com/hooks ep_acme-erp	invoice.*	Active
https://sync.example.net/in ep_ledger-sync	invoice.paid	Active
https://old.example.org/wh ep_legacy	All events	Disabled

Illustrative product interface

Monitoring and alerts

See success rate and latency per endpoint. When an endpoint keeps failing for 5 days, VelosCore disables it and emails your team and the endpoint owner, so one broken server does not keep piling up retries.

Delivery health for the last 24 hours with recent endpoint events

Success rate: 99.82%; Last 24 h
P95 latency: 184 ms; All endpoints
Failing endpoints: 1; Retrying

ep_acme-erp recovered after 2 failed attempts 14:07
Admin Secret rotated for ep_ledger-sync 11:40
ep_legacy disabled after 5 days of failures Yesterday

Illustrative product interface

Security and data handling

Encryption: TLS 1.2 or higher on every API call and every delivery. Payloads and endpoint secrets are encrypted at rest with AES-256.
API keys: Separate test and live keys. Keys can be scoped to read-only and revoked at any time from the dashboard.
Team roles: Owner, Admin, Developer and Viewer roles. Only Owners and Admins can see endpoint secrets or delete applications.
Export and deletion: Export message logs as JSON from the dashboard or API. Deleting an application removes its endpoints, messages and attempts within 30 days.
Retention: Payloads are deleted automatically after 3, 30 or 90 days depending on your plan. Delivery metadata without payload is kept for billing.
Support response: First reply within 2 business days on Developer, 1 business day on Growth and 4 hours on Scale, by email.

Try it with your own endpoints.

The Developer plan includes every feature on this page, with 25,000 events a month.

See pricing Talk to us