CodeHerald provides a new way to keep track of your code review queue, grouped by your next action needed.

When would you use CodeHerald?

• You work in a team that does code reviews.
• Your team receives ad-hoc code review requests via multiple channels: DMs, emails, bookmarks of filtered lists.
• Your team sometimes loses track of small pull requests, delaying them days.
• Your team find ad-hoc code review requests distracting, but cannot put a finger on why.
• Your team tried different strategies to improve code review process, and none of them felt right.

If any of the above is true, CodeHerald will help you.

What can CodeHerald do for you?

CodeHerald groups pull requests by next action: must review, needs an update, can be merged. It allows you to replace slack, emails, filters, and browser bookmarks with one single page that you can open at a glance and decide which PR to tackle next.

The wall

Every team with a real Postgres schema eventually hits the same wall: you need a populated database to develop, test, and demo — but you can't use production data. Either it's regulated (PII, PCI, HIPAA), or the company doesn't exist yet, or your distributed team isn't cleared to touch it.

The existing options are all bad:

• Anonymization tools start at $200K/year and take weeks to set up
• Seed scripts are fragile, break on every migration, and fill up with test@test.com
• Faker / Mockaroo have no foreign key awareness — falls apart past 10 related tables

The third option

Seedfast: realistic, relational data generated from your schema alone, no production access required.

Point Seedfast at your live Postgres, give it a natural-language scope (for example, "fintech app with 100 accounts, transactions, and varied balances"), and it fills your database in one CLI command. Foreign keys resolve automatically. Values are domain-appropriate — names look like names, transactions look like transactions, dates make sense. The same tool works for 10 rows in a unit test and hundreds of thousands in a load test.

Because nothing ever connects to production, there's no PII pipeline to maintain, no security review to clear, no compliance risk to mitigate. The compliance problem doesn't exist instead of being solved.

Who it's for

Teams that can't use production data:

• Regulated industries — fintech, healthcare, anyone under GDPR / HIPAA / SOC 2
• Early-stage teams without production data yet
• Distributed teams where not every engineer is cleared for prod
• Engineering teams of 5–50 — too small for enterprise TDM, too complex for hand-written seed scripts

Also a strong fit for any team with 20+ tables and a seed file that's quietly become tech debt nobody wants to own.

Postgres-first CLI, runs anywhere you can run a binary.

seedfast seed !