Lightweight Ruby web framework focusing on simplicity, performance, and convention over configuration
.svg){kind=logo}
Hanami is a modern, lightweight Ruby web framework designed for building clean, maintainable web applications with explicit control over code organization and structure. Created by Luca Guidi, Hanami emphasizes simplicity, modularity, and clear separation of concerns, making it ideal for developers and teams that value code clarity over conventions. The framework removes Rails' "magic," replacing it with straightforward Ruby code that's easy to understand, test, and modify without unexpected side effects.
Hanami's architecture centers on clear separation between HTTP concerns, business logic, and data access. The framework provides a lightweight router, view system, and utilities without imposing complex conventions or unnecessary features. Unlike Rails, which combines many concerns into models, Hanami encourages explicit, testable code through actions, repositories, and entities. This architectural clarity makes Hanami applications easier to understand, test, and maintain, especially as projects grow in complexity.
The Hanami ecosystem has matured significantly, with solid tooling for database integration (with Hanami Repositories), templating (Hanami Views), and testing. Hanami's lighter footprint makes it attractive for microservices, APIs, and applications where performance and simplicity matter more than Rails' comprehensive feature set. The framework appeals to developers frustrated with Rails' implicit behaviors and those building systems that require explicit, maintainable architecture from the start.
Hire Hanami developers when you need to build web applications emphasizing clean architecture and explicit code organization. If your team values understanding exactly what code does without relying on framework magic, Hanami developers bring this philosophy to every project. This is especially valuable for teams working on long-lived systems where code clarity directly impacts maintenance costs over years and decades.
Consider hiring Hanami developers when you're building microservices or APIs that need lightweight frameworks without Rails' overhead. Hanami's small footprint and explicit architecture make it ideal for services that handle single responsibilities without the complexity of full-featured frameworks. API developers appreciate Hanami's clear routing and serialization handling.
Hanami developers are valuable when you need applications that are easy to test and maintain. The framework's architecture encourages test-driven development, dependency injection, and clear separation of concerns. Teams prioritizing code quality and maintainability find Hanami developers bring these values to every aspect of development.
You should hire Hanami developers when transitioning from Rails or other frameworks. These developers understand why Hanami's explicit approach is superior for certain projects and can articulate the tradeoffs clearly. They often have Rails experience but have chosen Hanami for specific projects, bringing valuable perspective on when each framework is appropriate.
Must-haves: Strong Ruby fundamentals and ability to write clean, idiomatic code. Deep understanding of Hanami's architecture including actions, repositories, entities, and views. Ability to structure Hanami applications for scalability and clarity. Experience with Hanami's router, view system, and database integration. Knowledge of testing frameworks and practices in Hanami. Understanding of web development fundamentals including HTTP, REST design, and request-response cycles.
Nice-to-haves: Experience with Rails and perspective on when to use each framework. Familiarity with dependency injection patterns and how Hanami implements them. Experience building microservices or APIs with Hanami. Knowledge of database optimization and Hanami Repositories best practices. Experience with Hanami's testing features including features specs. Contributions to Hanami open-source projects. Understanding of architectural patterns like Domain-Driven Design.
Red flags: Inability to articulate Hanami's benefits over Rails or dismissiveness about explicit code. Poor understanding of web fundamentals or HTTP concepts. Lack of testing discipline or skepticism about test-driven development. Inability to design clean architectures or preference for "magic." Limited Ruby experience or writing non-idiomatic Ruby code. Resistance to learning new frameworks or flexibility in tool selection.
Junior developers: Should understand Hanami basics, create simple applications, work with actions and routes, and build basic views under guidance.
Mid-level developers: Can architect Hanami applications, design database schemas with repositories, implement complex business logic, design clean API endpoints, and mentor junior developers.
Senior developers: Can design sophisticated Hanami architectures, mentor teams on clean code principles, optimize performance, make strategic decisions about framework choice, and architect microservices.
Behavioral Questions:
Technical Questions:
Practical Questions:
Latin America: Hanami developers in Latin America typically earn $40,000 to $75,000 USD annually. Entry-level developers with basic Hanami experience earn $40,000-$50,000, mid-level developers with 3-5 years earn $55,000-$65,000, and senior architects command $65,000-$75,000. The Hanami community is smaller than Rails, so rates reflect specialized expertise.
United States: Hanami developers in the US earn $90,000 to $160,000 annually. The smaller community means specialized expertise commands premium rates. Mid-level developers earn $115,000-$140,000, while senior architects earn $140,000-$160,000 or more.
Latin American Hanami developers typically chose this framework deliberately after learning Rails or other frameworks, indicating thoughtful approach to tool selection and architecture. Many have worked on systems requiring clean, maintainable code and understand the importance of explicit, understandable architectures. The cost advantage—typically 40-60% less than US developers—is substantial while accessing developers with strong architectural thinking.
These developers bring international perspective on software development best practices and are experienced collaborating across time zones and cultures. Many actively contribute to Hanami open-source projects, staying current with best practices and emerging patterns. Their commitment to clean code and explicit design aligns well with Hanami's philosophy.
The time zone advantage enables continuous development cycles. While your North American team works, Latin American developers implement features, conduct code reviews, and push improvements. This accelerates development velocity and enables faster iteration on clean, maintainable code.
Latin America has a growing Hanami community with developers who deliberately chose the framework for its clarity and architectural benefits. These developers bring conviction about clean code and are excited to work on projects where these principles are valued.
Use Rails when you need rapid full-stack development with built-in features for admin panels, form handling, and comprehensive tooling. Use Hanami when you value explicit, understandable code and clean architecture more than framework conventions. Rails is better for rapid development. Hanami is better for long-lived applications where maintainability is critical. Many organizations start with Rails and graduate to Hanami as projects mature and complexity increases.
Yes. Hanami's explicit architecture scales better than Rails for complex applications because it avoids "magic" that becomes confusing at scale. The framework's modularity supports growing teams and evolving requirements without architectural pain.
Hanami is generally faster than Rails due to lighter footprint and less middleware. For most applications, the performance difference isn't the primary consideration—architecture and maintainability matter more. Hanami appeals to teams that value both clean code and reasonable performance.
Hanami Repositories provide an explicit data access layer that keeps application logic separate from database concerns. They encourage thinking about your database interactions explicitly, making applications easier to test and understand. Most Hanami applications use Repositories for all database access.
Yes. Hanami works well as an API backend for React, Vue, or other frontend frameworks. The framework's clean HTTP handling and clear API design make it excellent for headless applications serving modern JavaScript frontends.
When building a Hanami team, consider pairing developers with complementary expertise. Ruby specialists deepen language expertise. React or Vue developers integrate with Hanami APIs. Database specialists optimize data access layers. DevOps engineers handle deployment and infrastructure. Product managers help clarify requirements for clean implementation. You might also explore Ruby, React, and PostgreSQL for complementary skill sets.
