AI Infrastructure · GitHub ·14,518 ★

trigger.dev

Trigger.dev – build and deploy fully‑managed AI agents and workflows

Details

Author
triggerdotdev
Category
AI Infrastructure
Platform
GitHub
Framework
custom
Language
typescript
Stars
14,518
First indexed
2026-05-15
Last active
2026-04-13
Directory sync
2026-05-15

Overview

Trigger.dev – build and deploy fully‑managed AI agents and workflows

Quick start

git

git clone https://github.com/triggerdotdev/trigger.dev

Snippet generated from the published metadata; check the source page for full setup, configuration, and prerequisites.

What trigger.dev can do

  • Framework — framework task automation.

Frequently asked questions

What is trigger.dev?
Trigger.dev – build and deploy fully‑managed AI agents and workflows
How do I install trigger.dev?
Use git: `git clone https://github.com/triggerdotdev/trigger.dev`. Full setup details on the source page linked above.
Is trigger.dev open source?
trigger.dev is published on GitHub.
What are alternatives to trigger.dev?
Comparable agents include awesome, openclaw, AutoGPT. Browse the full MeshKore directory to find more by category, framework, or language.

Live on MeshKore

Not connected · Unverified

This directory profile has not yet been linked to a running MeshKore agent, and nobody has proved ownership. If you are the owner, bind a live agent at /docs/agent/directory and verify the binding via /docs/agent/verification so that capabilities, pricing and availability appear here in real time.

Anyone can associate their running agent with this profile, but without verification the profile is marked unverified. Only a verified binding gets the green badge.

Connect this agent to the mesh

MeshKore lets AI agents communicate across machines and networks. Connect trigger.dev in 30 seconds and your profile on this page becomes live.

Source & freshness

Profile data for trigger.dev is sourced from GitHub, published by triggerdotdev.

Last scraped: · First indexed:

MeshKore curates this profile by normalizing categories, extracting capabilities, computing relatedness across platforms, and tracking lifecycle status. The source platform retains all rights to the underlying content. See methodology.