Vercel Observability is the path of least resistance for teams whose entire production lives on Vercel. Logs, OTel traces, Web Vitals, Speed Insights — it is all there, lit up by default, and the developer experience is excellent inside that walled garden.
Cuitty is the answer when production is not, or not only, on Vercel. The wire protocol is HTTP. The data is yours. The modules can run on a t3.small, a Hetzner box, or your own k8s. Vercel can be one of the deployment targets the deploys module hits — but Cuitty does not assume it is the only one.
Feature parity
✓ supported · ~ partial · ✗ not supported. Notes link out to the relevant docs where useful.
| Capability | Cuitty | Vercel Observability |
|---|---|---|
| Runtime-agnostic Works regardless of where your apps run. | Yes | No Tied to the Vercel runtime. |
| Self-hostable | Yes | No SaaS, Vercel-only. |
| Zero-config for Vercel apps | Partial
Partial
OTLP exporter on Vercel works; needs one env var. | Yes On by default. |
| Logs | Yes OTLP-native, retains as long as you want. | Yes Tier-bounded retention. |
| Web Vitals / RUM | No Out of scope at 0.3. | Yes Speed Insights. |
| Tracing | Partial
Partial
OTLP pass-through. | Yes OTel-native. |
| Audit chain | Yes Notarized. | Partial
Partial
Audit log on Enterprise. |
| Identity + workspace RBAC | Yes SpiceDB. | Yes Team RBAC. |
| Secrets module | Yes Rotation engine. | Partial
Partial
Env vars; not a secrets product. |
| Deploys to non-Vercel targets | Yes AWS, GCP, Fly, k8s, bare metal. | No |
| Agent-native protocol | Yes | Partial
Partial
REST API; not agent-shaped. |
When to choose Vercel Observability
- Your stack is Vercel end-to-end and you intend to keep it that way.
- You want zero-config logs, traces, and Web Vitals out of the box.
- You are happy with tier-bounded retention and SaaS-only delivery.
- You do not have a data-residency story you have to argue with security about.
When to choose Cuitty
- Production runs on Fly, AWS, your VPC, your laptop — anywhere except (or in addition to) Vercel.
- You want a single observability surface that does not change shape when you add a non-Vercel deploy.
- You need a real secrets module, a real audit chain, and a real deploys module — not env-var screens.
- You are designing for AI agents and humans on the same protocol.
Migration path
Add Cuitty to a Vercel project
OpenTelemetry is the seam. Vercel projects can export to Cuitty without changing application code.
# Add to your Vercel environment variables, then redeploy.
OTEL_EXPORTER_OTLP_ENDPOINT="https://cuitty.example.com/v1/otlp"
OTEL_EXPORTER_OTLP_HEADERS="Authorization=Bearer ${CUITTY_TOKEN}"
OTEL_SERVICE_NAME="my-vercel-app"
OTEL_RESOURCE_ATTRIBUTES="deployment.environment=production"Verdict
Pick Vercel Observability if your stack is Vercel-only and you want zero setup. Pick Cuitty if you run anywhere else, or anywhere else *and* Vercel.