Viewing profile — eallam

Trigger.dev (YC W23), we are currently hiring for 3 roles: - Developer Relations Engineer | Hybrid UK or Europe remote | Full-time - Support Engineer | Hybrid UK or remote | Full-t…

Trigger.dev (YC W23) | Senior Backend Engineer | Hybrid UK or Remote (EET to PST) | Full-time We are an open source developer platform for building and running managed workflows an…

Mastra and Trigger.dev solve different but complementary problems. Mastra is great for building AI agents, with abstractions for reasoning, memory, tools and observability. Trigger…

Class act. Appreciated. > FWIW, more than 1/2 of our customers are AI agents, so it does make sense. We’ve seen the same thing, more even. Our positioning wasn’t even lead by our i…

That's great to hear, and thanks for the kind words. Sorry you had some issues migrating. You're right, it was our biggest docs update so far, and unfortunately a few things did ge…

Very common issues were: forgetting to put non-determistic code inside of steps (deterministic code can be put outside of steps, but non-deterministic = boom), incorrect use of cac…

That's actually how we started back during YC W23 as a "Zapier for developers" but we pivoted to "async workflows" later in 2023 and have since been used less like Zapier and more …

Currently we have two deployment models: self-host the entire platform or use our cloud offering, where we host the platform and your workloads. We've had a lot of feedback from us…

A couple things purely from the tech angle: - We're not really an agent framework, but more like a agent runtime that is agnostic to what framework you choose to run on our infra. …

Hi HN, I’m Eric, CTO at Trigger.dev ( https://trigger.dev ). We’re a developer platform for building and running AI agents and workflows, open-source under the Apache 2.0 license (…

Back in February, we posted a Show HN about building a “developer-first open source Zapier alternative” ( https://news.ycombinator.com/item?id=34610686 ). This was v1 of Trigger.de…

Eric from Trigger.dev here. We moved the docs from a dedicated repo into our monorepo so that probably accounts for the above issue