Connect to the tools you already run.
Signed webhooks, typed SDKs, and pre-built connectors for CI/CD, data warehouses, incident management, and Slack. Wire AuraOne into your stack in an afternoon.
Ecosystem
Pre-built connectors. Growing weekly.
CI/CD, data, incidents, observability, and collaboration. 16 connectors are GA/Beta today and new ones are added whenever a customer needs them.
Do not see yours? Use the webhook API to connect any system with an HTTP endpoint.
Capabilities
Four primitives. Clean contracts.
Webhooks, SDK calls, evidence exports, and metric forwarding. That is the entire surface area.
Signed webhook delivery
Signed payloads and retry policies for webhook events (implementation depends on your deployment and configuration).
SDK entry points
Trigger evaluations and workflows from CI, cron, or backend services. Typed clients for TypeScript and Python with environment-scoped config.
Evidence exports via API
Pull evidence bundles on demand, or configure scheduled exports to your storage (S3/GCS/Azure Blob as applicable).
Observability and metrics
Route evaluation signals into your dashboards and incident systems. Tracing and metrics depend on the stack you run AuraOne with.
Where it fits
Built for the stacks engineers actually use
CI pipelines, data warehouses, incident queues, and team channels.
Run evaluation suites as a gate in your release pipeline. Block deploys that fail safety checks.
Archive run outputs and evidence where your analysts already query. Parquet and JSON export supported.
Route high-severity findings to PagerDuty or Opsgenie. Attach evidence to the incident ticket automatically.
Post run summaries and action items to Slack or Teams. Link directly to the evidence bundle.
How it works
Events in. Actions out.
Pick the signals. Register endpoints. Route to your systems. Evidence stays attached at every step.
- Step 1Choose signals
Pick the events you care about: run.completed, review.escalated, export.ready, alert.created. Filter by project or severity.
- Step 2Register endpoints
Register destinations for the events you care about. Verification and signing settings are configurable by program.
- Step 3Route to your systems
Connect signals to the tools that own the response: incident management, dashboards, ticket queues, and archives.
// Express webhook handler with signature verification
import { createHmac } from "crypto";
app.post("/webhooks/auraone", (req, res) => {
const signature = req.headers["x-auraone-signature"];
const expected = createHmac("sha256", WEBHOOK_SECRET)
.update(JSON.stringify(req.body))
.digest("hex");
if (signature !== expected) return res.status(401).end();
const { event, data } = req.body;
if (event === "run.completed") {
// Archive evidence bundle
archiveToS3(data.evidenceUrl);
notifySlack(`Eval #${data.runId} passed.`);
}
res.status(200).json({ received: true });
});