Lucent
One bill for the four you're paying now — traces, errors, uptime, status page, and flags.
Useful when replacing: Sentry, Datadog, Statuspage, and LaunchDarkly
Pricing · USD
Own it
$99 once
Run it yourself or use optional managed hosting.
Hosted by us · optional
$9/mo
Cancel any month — it keeps running, because you own it. Or self-host and pay $0 forever.
$99 and it's yours as-is: MIT licensed, unlimited traces, events, hosts, status pages, flags, and seats. Deploy it today, or add hosting and updates for $9/mo. Want it instrumented across your services and agents properly? That's a Build Sprint. Nobody meters your traces, your errors, your hosts, or your users, ever — that's the whole point. Sentry, Datadog, Statuspage and LaunchDarkly will each bill you every month for the rest of your product's life.
Inside Lucent
The problem
Count what you pay to know whether your software is working. Sentry meters your errors. Datadog bills per host. Statuspage is cheap to start and climbs into the hundreds a month once your team grows. LaunchDarkly charges per seat and per active user for what is, underneath, a config lookup. Four vendors, four invoices, four dashboards that don't agree — and then agents arrive and none of them can tell you what a model actually did. Each one is a small piece of software. What compounds isn't the difficulty; it's the meter, and the number of separate meters.
How Lucent solves it
Full trace capture
Every tool call, model turn, and decision point recorded as a browsable, replayable trace — the part Sentry and Datadog were never designed for.
Errors, uptime, and a status page — same system
Exception tracking, release health, synthetic uptime checks from multiple regions, and a public status page your customers can subscribe to. All of it against the same events, in one system, with no per-event or per-host meter. The status page costs nothing, because rendering a page is not a business model.
Feature flags, without the per-user tax
Targeted rollouts, kill switches, percentage rollouts, and flags tied to the traces and errors they caused — so you can see the flag that broke the thing. Unlimited flags, unlimited seats, unlimited active users. It's a config lookup; charging per user for it was always absurd.
Self-hosted observability
Traces, errors, and stack frames are some of the most sensitive data you produce — they contain your customers' inputs. They stay on your infrastructure.
Cost and drift alerts
Get told when an agent's behavior or spend departs from its baseline — before a customer does.
Delivery terms — stated precisely
How Lucent is delivered, what you control, and where the boundaries sit.
Source included · MIT
Run it yourself or use optional managed hosting.
Data and hosting
Deploy in your cloud or use the stated optional managed-hosting plan. Data location and operator access are agreed before production use.
Compliance boundary
Residency, controls, and regulatory requirements are implementation decisions documented in the selected plan or delivery scope.
Rented vs. owned
The rented way
Sentry, Datadog, Statuspage, and LaunchDarkly
- Metered pricing that scales with your success, not the value
- Your data sits in their database, exportable only through their API
- Prices rise once you're integrated and can't leave
- Switching is a migration project nobody will approve
The Lucent way
$99 once — and then it's yours
- One price, paid once — hosting is $9/mo and optional, or $0 if you run it
- Self-host in your infrastructure, or use the optional managed plan under its stated data terms
- Source included · MIT — the exit terms are stated on this product
- Stop paying and nothing switches off. Leave with a git clone, not a support ticket
Built on
Lucent — the questions buyers ask
Who owns the code and IP?
For a Build Sprint, the repository, deployment assets, and work-product IP described in the SOW are handed over to you. Pre-existing products retain the licence shown on their product page; hosted services remain services. We state that boundary before work starts.
What happens if a sprint misses its scope?
We finish it. Fixed price means the risk of estimation is ours, not yours — a missed scope item is completed without a new invoice. Changes you request are re-scoped explicitly, so the line between 'our miss' and 'new ask' stays honest.
How do time zones work with a pod in India?
Every engagement includes 4+ hours of overlap with US or EU working hours. Async by default — written updates, weekly clickable demos — and meetings only when they earn the slot. You'll never chase a status report.
How is our data and code kept secure?
Work happens in your repos and your infrastructure wherever possible — we hold the minimum access needed, revoked at handover. NDAs are standard on request, and everything we self-host for you runs behind your keys, not ours.
How fast can you actually start?
Scoping takes a day; most sprints start within a week of sign-off. Pods are deliberately small and senior, so your start date is confirmed in the sprint plan — not left floating.
Do we need a retainer afterwards?
No — that's the point. A sprint ends with handover docs and training. If you want us to keep maintaining what we built, that's an optional flat monthly add-on you can cancel any month, because the software keeps working without us.
Own Lucent, don't rent it.
See the price, deploy on your infrastructure, keep the code. Or scope a sprint and we'll customise it and hand it over.