Plow — Building AI for everyone. One pivot at a time.

Live Stats

TOTAL TOKENS CONSUMED — ALL TIME

65,434,028,040

16.5B

7-DAY

48.9B

30-DAY

~$1.6M

SPEND / YR

SINCE INCORPORATION

3mo 9d 17h 47m 20s

DEVELOPMENT

COMMITS TODAY

11

LOC CHANGED TODAY

6.6k

TOTAL COMMITS

553

AI USAGE

TOKENS · 7 DAYS

16.5B

TOKENS · 30 DAYS

48.9B

PLOW USERS · LIVE

2,847

BUSINESS

REVENUE · MRR

$249

ACTIVE USERS · 7D

12

LIVE VIEWERS

1,269

BROADCAST

The Daily Yield Livestream
Join us every day at 2pm PST on Twitch

Daily Yield is where the Plow team shares what we’re learning as we build. Every day at 2pm PST we go live to break down practical workflows, experiments, and lessons from the front lines of AI.

The Daily Yield live — the Plow team on a video call

Want to submit a topic?

Join our Discord community ⟶

SAMPLE DAILY TOPICS WE COVER

Mon

2pm PST

The agent permission problem nobody has solved yet

Every agent needs access to do real things: your email, your files, your money. The industry is mostly ignoring the hard part — how do you grant access granularly, revoke it cleanly, and audit what ran without making the whole thing unusable? Containers and per-container permissions are the current best answer. What does that actually look like in practice?

Tue

2pm PST

Everyone’s vibe coding personal software. When does sharing it become the hard part?

The tools work. Anyone can spin up something custom in an afternoon. But the moment you want to hand it to someone else, the questions multiply: is it safe to run on their machine, does it work in their context, can they trust where it came from? Distribution is the unsolved layer. That’s the gap Plow fills.

Wed

2pm PST

The supply chain attack surface just exploded

When software is free and everyone is installing seeds from strangers, the old “only download from trusted sources” heuristic collapses. NPM-style dependency attacks, prompt injection in instructions, malicious seeds that look legitimate: this is the attack surface Plow’s trust layer is designed to address.

Thu

2pm PST

What does “deterministic” even mean when an AI agent is running your code?

Traditional software testing assumes repeatability. Agents introduce non-determinism at the execution layer. How do you QA a seed? How do you know if it worked? This is an unsolved and largely undiscussed problem that the Plow team is navigating in real time.

Fri

2pm PST

GitHub changed how the world writes software. Seeds need the same moment.

GitHub gave code a home: findable, forkable, with a trust signal baked in — stars, contributors, commit history. None of that exists for seeds yet. That’s the gap Plow is building into. What does the GitHub moment look like when the unit isn’t a repo, it’s an instruction file?

We’d love to have you on the podcast: AI Worth Using

World-class AI practitioners show exactly how they work. No predictions, no hype — just workflow. Hosted by Sam Odio & Tom Preston-Werner. Guests come straight off the leaderboard.