Aient is an AI SRE for your Vercel apps
Point a Vercel Drain at Aient and your function logs and traces flow straight into detection and remediation — no SDK, no code change. Aient reads the stack traces inside your Vercel errors, finds the root cause against your source, and opens a reviewed GitHub fix PR.
One-click ingestion
From a Vercel Drain to a fix PR
A Drain forwards telemetry Vercel already collects. Aient turns it into detected problems and, for crash-class issues, a reviewed pull request — without you instrumenting anything.
- 1
Add a Drain in Vercel
Generate a Drain URL and signing secret in Aient under Settings → Environments → Vercel Drains, then in Vercel go to Settings → Drains → Add Drain, choose Logs or Traces, and paste them into a Custom Endpoint.
- 2
Aient detects the problem
Vercel function errors and trace failures arrive in Aient and are grouped into scored problems — broad detection across logs and traces, no dashboards to build.
- 3
A reviewed fix PR lands
For crash-class problems, Aient investigates the root cause against your source code and opens a GitHub pull request. You review and merge; Aient then verifies the fix held in production.
The full step-by-step, with screenshots of Vercel's Add Drain flow, is in the Drain setup guide.
Logs and traces
Broad detection, crash-class auto-fix
Aient detects broadly across your Vercel logs and traces. Closed-loop auto-fix runs on the crash-class subset — exceptions that resolve to a stack frame in a repo Aient can read — and you can request remediation on anything else.
Logs
Vercel function logs — lambda, edge, build and more. Error and fatal records surface as problems, and the stack traces inside them feed automated root cause analysis.
Traces
OpenTelemetry traces over OTLP/HTTP. Aient ingests them as-is, keeping the project and deployment context Vercel attaches, so distributed errors show up with the spans behind them.
You stay in command
Aient proposes; you dispose
Each Drain URL is unique to your organisation, and Aient verifies a signatureon every request using a secret you set in Vercel. A leaked URL alone cannot be used to inject telemetry, and each organisation's data is isolated.
Remediation opens a reviewed GitHub pull request. It never merges for you — the merge button stays yours. After you merge, Aient watches production to confirm the problem is actually resolved, and reopens it if it regresses.
Pricing is the same as everywhere: EUR 99/month base plus usage for the AI work, with a budget you set. See the pricing page for how base-plus-usage billing applies.
FAQ
Questions, answered
How does Aient connect to Vercel?
What does Aient do with my Vercel logs and traces?
Will this reduce my MTTR?
Do I need both a Logs drain and a Traces drain?
Is it secure?
Does Vercel ingestion cost extra?
Get started
Connect your Vercel app in minutes
Add a Drain, paste the Aient URL and secret, and let Aient detect — and fix — what's breaking in production. You review every pull request before it ships.