Open Source at Clera

We open source the developer tooling we build to run our own infrastructure. Everything published here runs in production at Clera - no demos, no abandoned experiments.

How We Think About It

Why we publish what we publish - and what you can expect from anything we ship.

Build It, Then Share It

Every repo we open source started as something we needed internally. We don't build for an imagined audience - we publish what we use, and let the work speak.

Production-First

If it's on github.com/getclera, it runs in our production environment. No abandoned experiments, no toy projects - just the tooling we depend on every day.

Pay It Forward

Our stack is open source - Next.js, Drizzle, Trigger.dev, Typesense, and dozens more. Publishing back is the least we can do to keep that ecosystem healthy.

Contributions Welcome

PRs and issues get reviewed quickly - same pace we ship internally. Open an issue first for larger changes so we can align before you invest the time.

What We Build On

None of this exists without the open source projects we depend on every day.

Application

Next.js, React, TypeScript, Tailwind CSS, Biome, shadcn/ui.

Data & Search

PostgreSQL, Drizzle ORM, Typesense, dbt.

Background Jobs

Trigger.dev for everything async. Zod for runtime contracts.

AI & LLMs

Vercel AI SDK, Langfuse for observability, model-agnostic by design.

Open Source at Clera - FAQ

What we publish, why we publish it, and how to contribute.

We open source the developer tooling we build to run our own infrastructure - CLIs and Terraform modules for the third-party services we depend on (Trigger.dev, Typesense, Instantly). If we built it for ourselves and other engineers would benefit, we publish it. We don't open source the AI talent agent itself or anything that includes proprietary matching logic.

Two reasons. First, the tools we build for ourselves are usually better when other engineers can read them, file issues, and contribute - public scrutiny raises the bar. Second, we benefit enormously from the open source ecosystem (Next.js, Drizzle, Trigger.dev, Typesense, and many more). Publishing back is how we close the loop.

Yes. Every repo we publish runs in our production environment. We use trigger-cli to manage our Trigger.dev tasks, typesense-terraform to provision our search infrastructure, and instantly-cli/typesense-cli for daily operational work. If it's on github.com/getclera, we depend on it.

Absolutely. Issues and pull requests are welcome on every repo. We review contributions quickly and ship fast - the same way we work internally. For larger changes, open an issue first so we can align on the approach before you invest the time.

Our open source projects use permissive licenses (typically MIT) so you can use them in commercial products without friction. Check the LICENSE file in each repository for the exact terms.

Yes. As we build more internal tooling, we publish anything that's generally useful and not tied to our matching logic. The fastest way to see what's coming is to follow github.com/getclera.

Star a repo, file an issue, or send a PR. We'll see it.

Browse on GitHub

Work With Us