Co-Foundry Labs co-founds AI-native companies. We start ventures ourselves and with partners, build them on shared foundations we own, and give each one the freedom to stand on its own.
A foundry melts separate metals into an alloy and casts something that holds its own shape. We do the same with ideas, partners and platforms.
Ideas we fund and build in-house, each led by a founder who commits fully to it.
Built with partners who bring the technology, the domain or the market. Each runs as its own entity with its own brand.
The CRM & Ops platform and Core Assets, licensed to every venture, so none starts from zero.
Owned by Co-Foundry Labs and licensed under written terms. The same platforms are available to outside licensees and technology partners.
The operating system for community-led growth: leads, pipelines, partners, contracts, approvals and investors in one governed workspace. The foundry runs its own partnerships on it.
Common business services that stay critical however a company runs. Each can be used on its own by applications and AI agents, serves many subscribers from day one, and can be packaged inside a solution where regulation requires.
Partner services plug into Core Assets once. The CRM & Ops platform and every venture then consume them through the same governed interfaces, so partners reach every subscriber through one integration instead of many one-off builds.
Read the ISV partner architecture →We register as an ISV with each partner, starting with Twilio Trust Hub, and help each subscriber complete its own business verification with the partner.
Every customer is its own tenant with its own access policies, so one account's traffic never mixes with another's.
Customers bring their own business numbers or use platform default numbers we provision. Co-Foundry Labs uses its own numbers for its own communication.
Opt-in, consent, message content and channel rules are each subscriber's responsibility. Core Assets give them the tools to meet those rules; we facilitate the services.
Conversation and payment data stay with the customer's tenant and are never pooled or resold.
The foundry owns the integration, support escalation and roadmap with each ISV, across every venture that uses it.
Ventures appear here by name once both partners agree. Until then, this is where each one stands.
Co-founded with a technology partner. Partner commitment and the value each side adds are being validated.
Co-founded with a domain partner. In the same validation phase before the first gate.
Have the problem, the technology or the market? Bring it, and commit to it fully.
Start a conversationSpin-out is a designed ending. After it, a venture keeps licensing what it uses and the parent keeps its equity.
Problem, thesis and a committed partner or founder, on a small studio budget.
Gate 1 · validated problemBuild on Core Assets and the CRM & Ops platform; first customers; entity formed.
Gate 2 · paying usersReal revenue, its own team and brand, licences signed and critical IP in place.
Gate 3 · repeatable growthIts own cap table and investors. Licences travel with it.
We take operating responsibility for what we start: product, go-to-market, governance.
Every venture builds on common platforms and is designed to stand alone.
Pre-existing IP stays with its creator; what a venture creates is the venture's.
Perpetual licences that survive a spin-out. Leaving is always possible.
Related-party terms disclosed and approved, with the conflicted founder recused.
The foundry manages its partners and licences on its own platform.
An AI-native build speeds implementation and go-to-market for any venture mission.
Ventures pass gates on evidence, not enthusiasm.
Each door has its own terms, published in principle. Choose one and tell us a little about yourself.
Our integration and AI practice runs under its own brand. It helps businesses connect payments, messaging, voice and AI agents to the partner services they rely on, keeps the team sharp, and finds problems worth turning into companies.
Visit Labs Services ↗