Run your next project on one shared knowledge base
We are taking a small first cohort of teams of 2 to 20 engineers. You run one real project on Code4, where issues, reviews, documents, chat and calls feed one knowledge base that your team and your AI agents share. It is free during the program, we set it up with you, and you get a direct say in the roadmap.
What you would be trying
- Five sources are indexed into one base as they are written: issues, code reviews, documents, chat and call transcripts.
- Every answer runs under the permissions of the person who asks, and it names the source it came from.
- Your team asks it through the in-app assistant. Claude Code, Cursor or any MCP client reads the same base over MCP and works in your tracker with your permissions.
- Git hosting, pipelines and deploys sit in the same project, so the base follows the work from issue to deploy.
Built for small teams that build with AI
Code4 works best for 2 to 20 engineers on a new or young project, where one person can decide how the team works.
Dev agencies and studios
You start client projects often. Give each client one knowledge base, so every decision, review and call stays findable next to the repository, board and pipeline, instead of wiring five tools every time.
Early-stage startups
You are setting up engineering for the first time. Start with one knowledge base that your team and agents share from the first issue, instead of migrating off a patchwork later.
Small product teams
You are a few engineers who already write code with Claude Code, Cursor or Copilot. Give your agent the knowledge base, along with your issues, reviews and pipelines, through one MCP connection.
What you get
- Code4 at no charge for your whole team for the length of the program.
- A direct line to the founders. Your questions are answered by the people who build the product.
- Hands-on setup: we connect your repository and your coding agents to the knowledge base, move your first issues with you, and set up your first pipeline and deploy together.
- Your requests go to the top of the roadmap.
- A founding-partner discount when you move to a paid plan.
What we ask
- One real, active project on Code4, not a demo.
- A 30-minute check-in every week in the first month, then every two weeks.
- Honest feedback, especially about what is broken or missing.
- Optionally, a public case study, only if it works for you.
Good fit
- 2 to 20 engineers
- A new or young project
- Already coding with AI tools
- A founder, CTO or tech lead who can decide
Not the right fit yet
- Teams that need a security review or compliance certifications before onboarding
- Regulated data such as healthcare, licensed financial services or government
- Workflows built deep into another vendor's enterprise tooling
- Evaluating without a project to run
What is ready today
- A knowledge base over issues, code reviews, documents, chat and call transcripts, in the app and over MCP
- Issues, boards and sprints
- Documents with revisions and access rules
- Chat, threads and calls with transcripts and summaries
- Git hosting, code review and branch protection
- Pipelines with logs, tests and artifacts
- Environments, deploy approvals and rollbacks
- A package registry
- An assistant and an MCP server for your coding agents
What we will not pretend
There are no importers yet. We move your first issues with you by hand, and your code moves with a single git push.
There is no self-serve sign-up yet; access is granted per organization.
How to apply
- Send a short application by email. The template has nine one-line fields.
- Have a 20- to 30-minute fit call with a founder.
- Set up the project with us: your repository, the knowledge base for your coding agents over MCP, and your first pipeline and deploy.
Application template
- Name:
- Role:
- Company and website:
- Engineers on the team:
- Team type (agency or studio / startup / small product team / other):
- AI coding tools you use:
- Tools you use today for issues, git, CI and chat:
- The project you would start with:
- When you could start:
This opens an email in your mail app. Nothing is sent until you press Send.
Or write to support@code4.space. We reply to every application within 2 business days. If we record the fit call, we ask first. You can say no.
Leaving
You can leave at any time without giving a reason. Your repositories stay a git mirror away, and we export issues and documents for you on request.
Questions about the program
What is the design partner program?
A small first cohort of teams runs one real project on Code4 at no charge for the length of the program, with one knowledge base that the team and its AI agents share. We help with setup and put your requests first. In return we ask for a short check-in, weekly in the first month and then every two weeks, and honest feedback.
What happens when the program ends?
You choose. Move to a plan on the pricing page with a founding-partner discount, or leave and take your data with you. Nothing is charged until you choose a plan.
Do we have to leave GitHub?
No. Start with one new project on Code4 and keep everything else where it is. Code4 does not sync with GitHub today, so pick a project that can live in one place.
What happens to our data if we leave?
Your code is in git, so a mirror keeps a full copy at any time. Issues and documents are available through the API, and we export them on request. When a paid subscription ends, our terms give you 30 days to ask for an export.
Is it safe to let an AI agent near our deploys?
An agent you connect over MCP works with the permissions of the person who signed it in, so give it the access you are comfortable with. The branch protection rules you set hold for it as for that person. Required approvals apply to merge requests, so restrict push to a branch to make a merge request the only way into it. Protected environments wait for an approval before each deploy. The in-app assistant shows every tool call and asks before risky actions.
Can we use Claude Code or Cursor with it?
Yes. Code4 runs an MCP server: add it to your client, sign in, and your agent works with your permissions across issues, reviews, pipelines, docs and calls.
Ready to apply?
Send the application by email. A founder reads every one.
This opens an email in your mail app. Nothing is sent until you press Send.
Or write to support@code4.space. We reply to every application within 2 business days. If we record the fit call, we ask first. You can say no.