An infrastructure company with a portfolio of independently useful products.
Boundry is building infrastructure for applications and agents — a set of products that each address a distinct responsibility, and an integrated platform opportunity that emerges from their shared architecture.
Applications and agents need better infrastructure.
Software is increasingly built, extended, and operated by both people and agents. Models and APIs alone do not make that reliable. Applications and agents need dependable infrastructure for durable state, capabilities, authority, execution, and interoperability.
Boundry's thesis is that agents become more capable through better infrastructure, not simply through larger models — and that this infrastructure is best delivered as modular products with clear responsibilities rather than as a single monolithic platform.
That shapes the company: a portfolio of products, each independently useful, sharing a coherent architectural foundation.
Six products. Six responsibilities.
Products are organized by architectural responsibility. Each can be adopted independently; FeltKit integrates them into one developer platform.
What exists, and what is planned.
We distinguish carefully between capabilities that exist today and development that is planned. The product scopes below describe each product's defined responsibility.
| Product | Responsibility | Public site | Status |
|---|---|---|---|
| FeltDB | Durable state and control plane | feltdb.com | Shared in discussion |
| AppPort | Capability discovery and invocation | Not yet public | Shared in discussion |
| AppBoundry | Application boundary and portability | appboundry.com | Shared in discussion |
| AuthBoundry | Authority and delegation | authboundry.com | Shared in discussion |
| AgentBoundry | Agent execution and operation | agentboundry.com | Shared in discussion |
| FeltKit | Integrated developer experience | getfeltkit.com | Shared in discussion |
Detailed technical status, demonstrations, and evidence of working functionality for each product are provided directly in investment discussions. This page intentionally contains no customer, revenue, funding, partnership, or market-size claims.
Independent products and an integrated platform.
The portfolio structure creates more than one path to adoption. The opportunities below describe the potential of the model, not current commercial results.
Individual product adoption
Because each product addresses one responsibility, teams can adopt a single component — durable state, authority and delegation, or agent execution — to solve a specific problem without a platform commitment.
Integrated platform
FeltKit brings application development, durable state, capabilities, services, and deployment together. Teams that start with one product have a path to the integrated platform.
Shared foundations
Products that share an architecture reinforce one another: each additional product adopted adds value to those already in use, and new products can be added as the ecosystem evolves.
Potential distribution
Direct adoption by developers through each product's own website and documentation.
Commercial adoption of individual products or the integrated platform by teams building and operating applications and agents.
Integration by partners whose applications and agents benefit from explicit capabilities, authority, and execution controls.
Where the company is going.
- 01Independently useful productsContinue developing each product so it delivers value on its own.
- 02Shared contractsStrengthen the explicit interfaces that let products work together.
- 03Integrated platformBring the portfolio together through FeltKit.
- 04Ecosystem growthAdd products as new infrastructure responsibilities emerge.
This describes direction, not dated commitments. A detailed product roadmap is available in investment discussions.
Talk with Boundry.
For investment discussions, materials, or a technical walkthrough of the portfolio.