Promptise Foundry

Promptise Foundry gives you a complete, opinionated stack for building production agents, including a runtime, a tool server, and governance features like multi-tenancy and human approval gates. It is built for teams who need to ship complex systems with audit trails and security from day one. You get a lot in one install, but it doesn't offer file editing or browser control, which limits its use for general-purpose coding tasks.

This is not a drop-in coding assistant; it is a framework for building your own. Pick Promptise Foundry if you are building a new, agent-native product and want a coherent system for managing it. Pick CrewAI or Autogen if you need a more flexible, less-opinionated library to integrate into an existing project.

The product claims to be a full-stack agentic engineering framework. The repository shows it cannot edit multiple files or perform git operations. It offers a terminal and a Docker sandbox, but its ability to act on a codebase is limited. It is a framework for building agents, not an agent for building software.

This makes it a tool for creating tool-using agents in a constrained environment, not an autonomous software engineer. The focus is on governance, multi-tenancy, and tool discovery via its MCP server implementation. It provides a solid foundation for building governed, tool-using agents for other tasks.

Promptise Foundry is presented as a framework for constructing, deploying, and managing AI agents. Its architecture is composed of five documented subsystems: an Agent layer, a Reasoning Engine, an MCP Server SDK, an Agent Runtime, and governance features [2]. The design emphasizes production concerns such as multi-tenancy, security guardrails, and audit trails, which are often absent in agent prototypes [2]. The framework's utility is in providing these structural components, rather than offering a pre-built, functional software engineering agent.

The system's capabilities are therefore asserted, not demonstrated through benchmarks. The responsibility for implementing effective reasoning, context management, and tool use rests with the developer who adopts the framework. The absence of native file editing or version control capabilities means its application to software engineering tasks requires significant custom development [SPEC ROW]. It is a toolkit for building a house, not a house.

Promptise is positioning Foundry as a full-stack, 'one framework, not a dozen libraries' solution for agentic engineering. The feature set is impressive: multi-tenancy, governance, and a native MCP server SDK are all signals of a team that understands production requirements. They are clearly building for the enterprise, addressing pain points like state management, observability, and security that plague teams gluing together simpler libraries.

However, the current model is pure open-source with no revenue stream. This is classic venture-backed token burn to capture a developer base. The play is to build an indispensable tool, then monetize with a managed cloud service or enterprise edition. The risk is that the runway runs out before they can convert the community into paying customers. The likely acquirer is a major cloud provider looking to offer a turnkey agent development platform.

Promptise Foundry is an Apache-2.0 framework for building agents, not a hosted product. It offers components for multi-tenancy, audit capabilities, and human approval gates, which are necessary primitives. However, these are features we must build and maintain ourselves, not entitlements in a vendor contract.

This means we are responsible for the total cost of ownership: compute, storage, data retention policy implementation, and the engineering hours to build and operate the infrastructure. There is no vendor to call for an outage and no SSO to configure. All risk is internalized.

Promptise Foundry looks like a serious attempt at a full-stack agent framework. It's Apache-2.0, supports local models via Ollama, and has native MCP for both client and server, which I appreciate. The idea of a 'Reasoning Engine' with composable nodes instead of a basic ReAct loop is interesting, and the focus on production details like multi-tenancy and audit trails from the start is a good sign.

It's a Python framework you pip install, so you're running it on your own metal and paying your own model provider. The Docker sandbox for terminal execution is the right call for security. As long as the framework remains open and unencumbered, it has potential. The fact that I can read the source and run it offline is the main thing.