Roadmap · last updated July 2026
What we're building next
Seiri is a small product with a narrow job: tell you when scheduled work stops running. This page is our current thinking about what comes after that — not a commitment.
Phase 01
Shipped available today
The foundation — everything here is in production and covered by the free tier.
Standards-based sign-in, with scoped API keys for automation.
Create, edit, and delete monitors; track check-in status and delivery history.
An overview of every monitor, its schedule, and whether it checked in on time.
Installable and mobile-friendly, with the same experience on all three.
Phase 02
In progress being built now
Work that has started. We're reasonably confident these land, less confident about when.
Real-time dashboard
Seeing a check-in land the moment it happens, rather than after a refresh.
- Live activity feed over WebSocket
- Performance metrics and latency percentiles
- Configurable failure alerts
Interface improvements
Mostly unglamorous work on the things people use every day.
- Dark mode
- Keyboard shortcuts
- A better mobile experience
- Skeleton screens and progress indicators
Phase 03
Next planned, not started
Agreed in principle and specced loosely. Order and scope are both still open.
Search and filtering
Useful once you have more monitors than fit on one screen.
- Full-text search with fuzzy matching
- Saved searches and auto-complete
- Multi-dimensional filtering with boolean rules
- CSV and JSON export
Templates and setup shortcuts
Most people are monitoring the same handful of things. We'd like to skip the boilerplate.
- Templates for common sources (Stripe, GitHub, Shopify)
- Custom templates you can share
- A testing playground for check-ins
- Code generation and Postman collection export
Teams and larger accounts
We get asked for these regularly. They're real work, and we won't claim any of them until they exist — including the certifications.
- SSO (SAML, LDAP)
- Audit logging and IP allowlisting
- Team workspaces, comments, activity feeds
- Data residency options and documented disaster recovery
Phase 04
In planning early
Areas we're actively scoping. These sit behind the work above, and the shape of each will change as we learn more — but they're on the plan, not just on a list somewhere.
Anomaly detection
Flagging a job that still checks in but has started finishing far later than it used to. Genuinely useful if it works, and noisy if it doesn't — so we'd rather ship nothing than ship a source of false alerts.
More ways to check in
Message queues, serverless functions, and event streams as first-class check-in sources, alongside HTTP and email.
Reporting
A report builder and data-warehouse export, for teams that need to show someone else that the jobs ran.
More regions
Additional deployment regions, driven by where customers actually are and what their data-protection rules require — not by a map with pins in it.
Principles
What we optimise for
We don't publish user or revenue targets. These are the things we'd actually be embarrassed to get wrong.
Not missing an alert
The one thing Seiri cannot do is stay quiet when your job went silent. Everything else is negotiable.
Not crying wolf
An alerting tool people have learned to ignore is worse than no alerting tool. We'd rather add a feature slowly than add noise quickly.
Staying small enough to understand
One line of curl should stay enough to get started. If a feature makes the first five minutes harder, it needs to earn that.
Being honest about status
No feature is described as available until it is. If we're behind, this page should say so before you have to ask.
Feedback
Tell us we've got this wrong
The ordering above is a guess. If you're running something Seiri doesn't handle well, that's more useful to us than any of it — and it's usually what changes our priorities.
Email hello@seiri.app. It reaches the people who build it, and we read everything. We usually reply within a few days — if it's urgent, say so in the subject line and we'll get to it sooner.
Email the team