Sourcebot3 min read Auto

Inside Sourcebot: what it does, who built it, and what it raised

Sourcebot indexes an organisation's entire codebase and answers questions across all of it at once. It runs on your own infrastructure, which is the whole point for teams whose source is not allowed to leave the building.

Compiled automatically from public sources — the company's own posts, launch material and reporting, all linked at the bottom. The “what using it looks like” section is a walkthrough built from public documentation, not a first-hand review. If this is your company, claim the page and correct anything wrong.

The problem they picked

Code intelligence tools mostly share one shape. Send us your repositories, we index them in our cloud, you get search and an assistant.

For a lot of companies that sentence ends the evaluation. If you build chips or weapons or run hospitals, your source is not going into someone else's account. No amount of SOC 2 moves that.

Sourcebot builds for the people who say no. And for a second group that's easier to miss: teams whose codebase is simply too large for tools that assume one repository at a time.

What it actually is

Open source, self-hosted. You run a Docker container inside your own infrastructure, point it at every repository the company owns, and it indexes all of them together.

Two capabilities that usually ship separately. There's precise search, with regex and boolean queries across the full index, the kind you reach for when you know the exact token you're hunting. And there's plain-English questions answered against the indexed code, grounded in what's actually in your repositories rather than a model's memory of open-source Python.

Pairing them is the point. Retrieval on its own invents things. A regex box, however fast, still requires you to already know what you're looking for.

They report use at NVIDIA, Red Hat, Wikimedia and Arista Networks. Large organisations that also can't touch the hosted alternatives.

What using it looks like

Built from Sourcebot's documentation, launch post and open-source repository. A walkthrough, not a first-hand review. Auto-generated and correctable.

Setup is the part they clearly worked on. One Docker container, a config file listing your repositories from GitHub, GitLab, Gitea or local paths, and indexing runs from there. No ceremony per repository. For a company with four hundred of them, that's the difference between an afternoon and a rollout that needs its own project manager.

Once indexed, the two modes sit next to each other. Regex search behaves the way anyone who lives in a large codebase expects: fast, exact, scoped by repository or path, returning every hit instead of a ranked guess. The natural-language mode takes something like "where do we validate webhook signatures" and answers with citations to specific files.

Self-hosting cuts both ways. Nothing leaves your network, which is the entire reason the product exists. You also own the box, the index freshness and the upgrade. That trade only makes sense when your security posture already made the decision for you, and for the customers they name, it did.

The news

Fall 2025, Y Combinator F25, and a $500K seed with Pioneer Fund and Team Ignite Ventures alongside YC.

Small for the batch. It fits a company that's open source first and selling into enterprises rather than buying growth.

The sequencing is what I'd pay attention to. NVIDIA and Red Hat were using it before the money arrived. In developer tools that's the order you want.

Funding

$500Ktotal raised
DateRoundAmountInvestors
Oct 2025Seed$500KY Combinator, Pioneer Fund, Team Ignite Ventures source

Who's behind it

Brendan Kellam and Michael Sukkarieh met in their first week at McGill, both already deep in game engines. That took them to Ubisoft Montreal, then Visual Studio at Microsoft, a cloud-first game engine at Google, VR operating systems at Meta, and cloud-streaming infrastructure at Xbox.

Every one of those is a codebase where "just read the code" stops being advice. They're building the thing they kept wanting.

Founders

  • Brendan KellamCo-founder

    Game engines at Ubisoft Montreal, then Visual Studio at Microsoft and cloud-streaming infrastructure at Xbox.

  • Michael SukkariehCo-founder

    Ubisoft Montreal, then a cloud-first game engine at Google and VR operating systems at Meta.

Why it might not work

Self-hosted is a moat and a tax at the same time. Cloud competitors ship improvements every week. Sourcebot ships when a customer's platform team schedules the upgrade.

And the incumbents keep absorbing adjacent features into the IDE. The bet is that "your code never leaves the building" stays a hard requirement for a large enough market, rather than fading as people get used to trusting vendors. I'd take that bet. I'd still want to know how big that market really is.

Sources