Prefect

Prefect

@prefect.io

Modern workflow orchestration for data and ML engineers.

506 followers42 following111 posts

Here's to the open source holding up Prefect, Dagster and FastMCP. pytest runs our tests. SQLAlchemy handles our databases. PyO3 connects Python to Rust. structlog keeps Dagster's logs in order. To the people behind them and many more: thank you. www.prefect.io/blog/prefect...

prefect.ioPrefect's open source sponsorship: 2026 updatePrefect gave $40,000 to 12 open source maintainers, project teams, and collectives in 2026, supporting the libraries behind Prefect, Dagster, and FastMCP.

fastmcp 4.2.0a1 is out: skill issue. serve skills over mcp alongside your tools. point fastmcp at your skills folder; clients can discover and download them. uv add --upgrade 'fastmcp==4.2.0a1' --prerelease=allow

skills travel through mounts and proxies, too. clients can discover skills across servers and save them locally. enable skill discovery on a proxy with skills=True.

Prefect reposted

First time all together in person. We were more than a little excited, so we went to New Orleans. We swapped stories, made big plans, and went home as one happy team. We’ll share those big plans soon. Stay tuned. Thank you, NOLA.

Prefect reposted

🤩 our MCP contributor community

straight from dbt summit 2026: we asked our floor reps what customers wanted to talk to them about. watch what they heard about ai agents, data freshness, and mcp servers last week in vegas.

It’s almost time for dbt Summit 2026, and we’ve got Prefect, Dagster, and FastMCP people all in one booth. Find us for demos, conversations about orchestrating dbt, data assets, MCP, and a****** workflows. + some customizable swag Link in comments for more. *The a-word is agentic, obviously.

"I'm something of an admin myself." On the latest episode of FastMCP Pod, Jeremiah Lowin walks through MCP authentication / authorization and how FastMCP actually checks you out. Full episode in the comments below ⤵️

C is for Context. And that's not good enough for most people. "Context" gets confusing fast. Context window, context engineering, model context, server context... one word doing a dozen jobs. So we gave it a whole episode. @jlowin.dev and Radhika pull the meanings apart, one at a time. Link Below.

The DAG is dead. Long live the DAG. Same name, new job. The old workflow graph cared about how work got done. @jlowin.dev take at PyData London: graph the outcome. Stop auditing the loop and audit what falls out of it. Full keynote talk from PyData London below ⤵️

Running MCP with no gateway? Crazy. Running across the Grand Canyon and back? Somehow less crazy?! Fokke Dekker and Zach Angell talk Prefect Horizon, our enterprise MCP gateway, on Prefect's annual morning run before all-hands. Get a secure MCP server URL, free. Link Below →

We're in a new season of the FastMCP Pod and we're calling it Summer School. Everyone says "MCP gateway." Almost no one means the same thing by it. So we're going back to class. Jeremiah Lowin @jlowin.dev and Radhika Gulati get into what it actually is. Full Class recording in the comments ⤵️

New headshots from the Prefect team, dropping today. Scientists call it the Pre-effect: a glow-up that kicks in once you join. Cause: immediate exposure to workflow automation. Effect? Undeniable.

View full thread

BUT WAIT, THERE'S MORE! Claim a free hat while supplies last. Limited edition run, going fast. Visit the launch site below to claim yours. ☟ 𝘚𝘦𝘭𝘦𝘤𝘵 𝘧𝘦𝘢𝘵𝘶𝘳𝘦𝘴 𝘢𝘷𝘢𝘪𝘭𝘢𝘣𝘭𝘦 𝘪𝘯 𝘰𝘱𝘦𝘯 𝘴𝘰𝘶𝘳𝘤𝘦. 𝘔𝘢𝘺 𝘤𝘢𝘶𝘴𝘦 𝘴𝘶𝘥𝘥𝘦𝘯 𝘶𝘳𝘨𝘦𝘴 𝘵𝘰 𝘥𝘦𝘭𝘦𝘵𝘦 𝘺𝘰𝘶𝘳 𝘰𝘭𝘥 𝘰𝘳𝘤𝘩𝘦𝘴𝘵𝘳𝘢𝘵𝘰𝘳. 𝘚𝘰𝘮𝘦 𝘧𝘦𝘢𝘵𝘶𝘳𝘦𝘴 𝘪𝘯 𝘰𝘱𝘦𝘯 𝘣𝘦𝘵𝘢. 𝘓𝘢𝘴𝘵 𝘥𝘢𝘺 𝘰𝘧 𝘭𝘢𝘶𝘯𝘤𝘩 𝘸𝘦𝘦𝘬.

Some of the hits include: - Managed Automations (no more zombie runs) - Config Plugins (pip-install your environment) - Workspace Personalization (only see what's yours) - Infrastructure Debugging (see OOMs in the UI) - Assets Explorer (look up an asset and its history) - ...and 6 more

View full thread

Watch how to: - plan the DAG into parallel waves for faster execution - retry individual nodes so one failure doesn't stop runs - use persistent caching to skip work and save compute

Friends don't let friends re-run unchanged SQL. It’s Day 2 of launch week and today we're launching the Prefect dbt Orchestrator. Every model, seed, test, and snapshot runs as a Prefect task. Caching, per-node retries, and the same alerting your other Prefect work uses.

View full thread

4. dbt inherits Prefect’s orchestration primitives The same caching, retries, alerting, and visibility you use for Prefect flows now apply to dbt workloads.

Friends don't let friends re-run unchanged SQL. It’s Day 2 of launch week and today we're launching the Prefect dbt Orchestrator. Every model, seed, test, and snapshot runs as a Prefect task. Caching, per-node retries, and the same alerting your other Prefect work uses.

View full thread

2. The DAG keeps moving when a model fails A staging model fails. Prefect retries that node without restarting the entire build. Other branches keep running.

3. Parallel execution without the overhead Prefect executes independent nodes concurrently instead of treating dbt build as one giant batch job.

Friends don't let friends re-run unchanged SQL. It’s Day 2 of launch week and today we're launching the Prefect dbt Orchestrator. Every model, seed, test, and snapshot runs as a Prefect task. Caching, per-node retries, and the same alerting your other Prefect work uses.

1. Stop running the same SQL twice Each node’s SQL, config, macros, and upstream dependencies are hashed. If nothing changed, Prefect skips the node.