Open architecture framework

Keel is the architecture that lets you focus entirely on the business logic.

Keel Framework is an open source initiative dedicated to defining and standardizing software architectures on top of mature technologies such as Spring, Apache or Python. It provides reference architectures for enterprise environments that encapsulate the technical and cross-cutting capabilities (security, session, integration, observability), so that each project only has to build what is specific to it.

How Keel works

One architecture. Different technologies. Different use cases.

Keel starts from a simple idea: projects should not have to solve the same problems of architecture, infrastructure and cross-cutting capabilities over and over again.

Every framework in the Keel family applies the same method: start from a mature base technology, establish a reference architecture on top of it and turn the common decisions into reusable capabilities.

Keel ecosystem: 1 foundation technologies, 2 cross-cutting layer, 3 use-case frameworks
01

Foundation technologies

Keel does not try to replace the technologies it is built on.

It starts from mature ecosystems widely used in production, such as Spring, Apache or Python, and uses their capabilities instead of reinventing them.

The base technology provides the infrastructure.
Keel establishes how to use it consistently.

02

The Keel layer

On that foundation, Keel defines a reference architecture and encapsulates in independent modules the capabilities that are common to many projects.

Security, observability, transport, configuration, integration and other cross-cutting capabilities stop being decisions each team has to solve from scratch.

Keel also establishes development conventions, modular composition and centralized version management through BOMs, providing a common technical base for projects.

03

Frameworks by use case

From that architecture, specialized frameworks are built for concrete needs.

Each framework combines the technology foundation with the Keel capabilities and also provides the scaffolding needed to generate a project ready to develop the business logic and deploy it.

Today, that application is Keel MCP, aimed at building Model Context Protocol servers. Tomorrow, the same architecture can extend to new use cases and technologies.

The use case changes.
The architectural philosophy remains.

The architecture model

Technology inside. Domain above. Keel decides how they fit together.

The Keel architecture encompasses the choice of the foundation technology and the modules and conventions built on top of it. Your application rests on that whole and only adds the domain.

Your domain
Business logic · Use cases · APIs
Project-specific behavior and domain decisions.
↓
Keel architecture
Keel modules & conventions
Architecture · Conventions · Cross-cutting capabilities
Security · Observability · Transport · Configuration · Integration
↓
Foundation technology
Spring · Python · Apache · …
Mature infrastructure and runtime capabilities.
Available today

Keel MCP

A framework for building production-ready Model Context Protocol servers. It applies the Keel architecture to the MCP use case and provides the project scaffolding so that developers can start directly with the domain logic. Available for Java; the Python version is planned for December 2026.

Reference architectureLayered modular structure and clear conventions.
Two foundation technologiesJava 25 · Spring Boot 4 · Spring AI (available) and Python · FastMCP (planned).
Cross-cutting modulesJWT/OIDC security, MCP session, Streamable HTTP transport, cache and observability.
Project scaffoldingA Maven Archetype that generates an MCP Server ready to develop.

Build the domain. Keel the architecture.

The use case evolves. The technology can change. The architectural principles remain consistent.

Explore the ecosystem ↗