During the months since, we’ve gathered a lot of feedback from early users and realized that what developers actually wanted was more like an easier-to-use Temporal with integrations.
Here’s what we’ve learned so far:
- Serverless timeouts make it hard for anyone to write reliable background jobs. So our current product makes that easy for Next.js and other full-stack React frameworks. Long-running server support is coming soon.
- We simplified the architecture to make it far easier to self-host. This was the most common comment in our previous Show HN.
- We made it much easier to contribute to. You can now add new API integrations for any service we don’t already support. Either publicly (we appreciate PRs) or privately in your existing codebase.
We’re open about what we’re building (https://trigger.dev/changelog) and what we’re planning on doing next (https://trigger.dev#roadmap) as we believe community feedback ensures that we’re solving real problems.
So here’s where we’re at, and where we’re headed:
[x] Easy self-hosting.
[x] Serverless. Long-running Jobs on your serverless backend.
[x] Integration kit. Build your own integrations, or use ours.
[x] Bring-Your-Own-Auth. You can now authenticate integrations as your users.
[x] Dashboard. View every Task in every Run.
[x] Cloud service. No deployment required.
[x] React hooks. Easily update your UI with Job progress.
[x] React frameworks. Support for Next.js, Astro, Remix, Express.
[ ] More frameworks. Support for SvelteKit, Nuxt.js, Fastify, Redwood.
[ ] Background functions. Offload long or intense tasks to our infrastructure.
[ ] Long-running servers. Use Trigger.dev from your long-running backend.
[ ] Polling Triggers. Subscribe to changes without webhooks.
[ ] And lots more…