Nuntilo for developers
It speaks your stack.
Build on the Nuntilo API. GitHub, Slack, and Linear aren't afterthoughts here — they're first-class channels, right alongside the phone. Wire your tools into one place, describe what should happen in plain English, test it like you'd test anything else, and keep a hand on the gate. We're building Nuntilo for developers first, because we are ones.
- GitHubworkflow failed on mainnow
- GitHubPR #482 merged3m
- LinearVIZ-231 created · “Onboarding bug”12m
- Slackmessage in #support20m
- GitHubrelease v0.31 published1h
Your tools, as channels
The events you care about — not the firehose.
Connect a repo, a workspace, a team — Nuntilo watches a curated set of events, not a notification storm. A failed CI run, a merged PR, a new Linear issue, a message in #support: each becomes something you can reason about, route, and act on from one place — the same place your calls, texts, and email already land.
- GitHub: workflow failures, merged PRs, opened issues, published releases.
- Linear: issues created, updated, closed, and commented.
- Slack: messages in the channels you choose to watch.
- GitHubworkflow failed on mainnow
- GitHubPR #482 merged3m
- LinearVIZ-231 created · “Onboarding bug”12m
- Slackmessage in #support20m
- GitHubrelease v0.31 published1h
In plain English
“When CI fails on main, tell #ops — at most once an hour.”
github.workflow_failed
a CI run fails
branch is main
condition
slack.notify · #ops
auto · at most once / hour
Automations in plain English
Describe it. Read the plan. Approve it.
Write the intent and Nuntilo compiles it into named rules you can see and reason about — with operators, groups, rate limits, and multi-step chaining underneath when you need them. See the automation builder.
- “When CI fails on main, tell #ops — at most once an hour.”
- Compiled into a visual trigger → condition → action plan.
- Conditions, cooldowns, thresholds, chaining — expressive, no DSL to learn.
The test loop
A dry-run harness that can't lie to you.
You already know why this matters: a test that runs a different code path than production isn't a test. Nuntilo's dry-run harness executes the exact rule engine the live system uses — no reimplementation, no drift. Simulate github.workflow_failed, watch each clause pass or fail, and read the message it would post — all with zero side effects.
- Feed a rule a sample payload; see the clause-by-clause evaluation.
- See the literal delivery it would send — before it sends anything.
- Same evaluator as the live wheel. Green in the test means green in production.
Simulate an event — the same judgment the live wheel runs, no side effects.
- ✓branch == main
- ✓conclusion == failure
Would deliver
#ops — “CI failed on main · build #4821”
Event
github.workflow_failed received
Synthesis
matches “Notify ops on CI failure”
Gate
auto — confidence 0.91 over threshold
Reaction
posted to #ops
Gated and auditable
Ship-safe by construction.
Notifying your own team is one thing; opening a public issue or emailing a customer is another. The gate knows the difference, and holds the second kind for your sign-off — nothing customer-facing goes out without your yes. And nothing is a black box — every decision records why it was made, so you can audit Nuntilo like you'd audit any other service.
- Internal actions auto-fire; anything customer-facing waits at the gate.
- Every run leaves an append-only trail: event → decision → gate → action.
- Read exactly why anything happened — the match, the confidence, the result.
Why developers first
We dogfood it on ourselves.
Nuntilo watches its own repos, routes its own CI, and files its own issues. The beachhead isn't a marketing choice — it's the team using the product to build the product.
Labs
Built in the open
We write up the architecture and the debugging as we go. Read the engineering notes.
Direct line
You shape the roadmap
Early developers get a direct line to the team. The gaps you hit are the next things we build.
Not just dev tools
One inbox, still
The same phone carries calls, texts, and email — so the business side of solo dev life lands in one place too. See the inbox.
Your tools already emit everything that matters. Nuntilo reads it, acts on it, and asks you before it does anything you'd want to be asked about.
Wire up your stack.
Join the waitlist — we're onboarding developers and technical founders first.