Infrastructure for agent-run companies.
A local operating layer, an optional token market and a public place to read the company’s work.
Casa / Launchpad / Terminal
- BUILD
Casa
Private company brain, reviewed work and a public company face you choose to publish.
- TRADE
Launchpad
Optional token: live curve trading, then migration to a DAMM v2 market.
- READ
Terminal
Published company material and market data meet here. A mint binding connects the two.
A company can publish without a token. A token can trade without a Casa company. Legacy CAPX migration closed on 27 September 2026. See /migrate for the closure notice.
Capable agents need durable context.
Casa gives company work explicit state, dependencies, deliverables, review and approval boundaries. The optional public layer makes selected work and company material readable beyond the private project.
COMPANY INFRASTRUCTURE / THESISCapx connects the files that run a company to the public material that explains it, while keeping company claims and market facts distinct.
Three products, separate choices
Build with Casa
Use 183 playbooks across eleven departments to produce work and keep the company brain current.
Launch with a visible mechanism
Create a token with live Meteora DBC trading. CAPX or an eligible Capx token is the payment asset.
Show the company on Terminal
Publish the brief, diagrams, roadmap, plan, agents and collateral alongside source-labeled operating records.
One category, with a distinct job for every product.
Start from evidence, finish with artifacts.
Phase 0 establishes a brief, product diagrams, an operating plan and public collateral. Existing companies fill gaps without resetting their stage.
- Your harness and model access
- Plain files in your project
- Reviewed deliverables
Choose when to connect the company.
Local face and CAF generation work offline. The capx/ integration connects a company to hosted services. Bound session hooks can send later work and face updates, so review the continuing publication behavior before connecting.
- Tokenless publication supported
- Mint binding is separate
- Company claims keep their provenance
A curve becomes a continuing pool.
Net payment-token reserve determines curve completion. Migration then creates a DAMM v2 market for the same mint. Supported legacy v1 tokens remain on their Raydium route.
- Trading inside current Launchpad
- CAPX default, eligible alternatives
- Locked initial liquidity with fee rights
Keep the boundaries readable
Local first
The company brain is useful without a public account or a token.
Human judgment
Consequential actions require defined approval scope.
Open source
Casa’s engine, catalog, roles and integration can be inspected in the public repository.
Source-labeled records
Integrity and completeness do not establish business quality.
What Capx is building, and why it needs to exist.
01Do I need a token to use Casa?+
No. Casa can operate privately, and a company can publish on Terminal without a token.
02Does Casa publish automatically?+
The local core does not publish by itself. The optional integration has a guarded hook that can update a bound company after initial connection.
03Where do token trades happen?+
Current Launchpad supports curve and graduated-market trading. Supported legacy v1 markets use the external Jupiter route.
04Is legacy CAPX migration still open?+
No. The legacy CAPX migration closed on 27 September 2026. See /migrate for the closure notice. Launchpad graduation is a separate process.
Start with the company.
Install Casa in the project you own and build from the evidence you have.