Skip to content
We Can Just Build Things
Build Plate Freedom-tech fabrication · open source · rev 2026

We Can Just Build Things

You can just build things. Tools that protect your community — made with an AI agent, grounded in verified freedom tech, and accountable to the people who depend on them.

Open the Build Studio Browse the catalog New here? Start with the basics
Catalog
1,300+ verified tools
License
checked @ commit
Owner
the movement
Agent
bring your own

For the people who build to protect their communities

Section titled “For the people who build to protect their communities”

An organizer who needs to document evictions without exposing tenants. A collective building a tool their members can actually trust. A nonprofit shipping something real with a tiny team. You bring the intent and the knowledge of what your community needs — an AI agent and this project bring everything else, so what you ship is indistinguishable from the work of a professional team.

A harness like Goose or Claude Code gives the agent hands. This gives it judgment: a verified catalog of freedom-tech tools, a guided flow from idea to shipped, reusable agent skills, and safeguards that have your back — so when the agent runs, it builds on decisions already made, verified, and documented.

  1. Build what your community needs

    You don’t need a CS degree — only to know the problem. Say it in plain words, and the guided flow plus an AI agent take you from “my community needs this” to a shipped, production-grade tool.

  2. Check every claim yourself

    Every tool’s license is verified at a specific commit, with the receipt right on the page. You never take a vendor’s — or a README’s — word for what you depend on.

  3. Your values, kept by default

    The tools you build to protect your people can’t be quietly wired into surveillance-ad stacks. Anything owned by Meta, OpenAI, or xAI is kept out — automatically — so solidarity is the default, not a chore.

  4. Built to outlast its makers

    Made for month six, not demo day. Weekly checks keep the catalog honest, and anyone can fork the whole project and keep going — the infrastructure belongs to the movement, not one maintainer.

Built for you, not for the platform

Section titled “Built for you, not for the platform”

This is not built for the founder who already owns the agent network and sets the norms. It’s built for the organizer, the nonprofit, the collective — the people who have to trust a system without being able to see inside it, and who deserve to make the calls about what they depend on with their eyes open. The safeguards exist to serve them, never to fence them in.

  1. The first-time builder

    You have an idea and a community problem, not a CS degree. Follow the guided flow from intent to a shortlist of vetted tools — and on to something shipped.

  2. The builder-operator

    You already ship. Check a license, find adjacent libraries, grab a configuration recipe — and save an afternoon of due diligence.

Use the tools

Section titled “Use the tools”

  1. Build Studio →

    Describe your project; get a policy-clean stack, a constitution, an agent prompt, and a starter repo you can download.

  2. Catalog explorer →

    Search a thousand-plus verified tools and 800+ datasets — by what they do, the network they run on, and their license.

  3. Check a dependency →

    Paste your dependency list; we check it against the blocklist right here on your device — nothing is uploaded. License details are looked up live; only the package names travel.

  4. The build flow →

    From “my community has a problem” to a plan you can actually ship.

Start where you are

Section titled “Start where you are”

  1. What this is →

    The 3-minute orientation.

  2. Why not just use Goose? →

    The harness vs. the layer that gives it judgment.

  3. How we keep our promise →

    The safeguards that protect what you build, in plain language.