Open Source Platform framework for Spring teams

Ship services with platform DNA.

Built for teams managing multiple Spring Boot repositories that need a more consistent platform baseline.

Getting Started

Install the CLI with Homebrew, generate a Spring service, and run it locally.

CLI Commands

From your terminal:

# install the Helix CLI
brew tap helixframework/helix
brew install helix-cli

# generate a Spring service
helix init springboot payment-service

# run it
cd payment-service
./gradlew bootRun

Want the full setup flow, template options, and CLI reference? Head into the docs next.

Getting Started CLI Reference

Why Standardization Matters

Most platform pain does not start with one dramatic failure. It starts with small inconsistencies that multiply across repositories until every new service, upgrade, and support issue costs more than it should.

Without a shared framework layer

Teams usually end up rebuilding the same platform decisions in slightly different ways.

New services start from different repo shapes and setup patterns
Build rules drift across projects until standards become optional
Observability, rollout, and support capabilities get reimplemented unevenly
Upgrades turn into repo-by-repo cleanup instead of a platform improvement

With Helix

Teams start from a known baseline and evolve from shared platform decisions instead of one-off reinvention.

Projects begin from versioned templates that already match platform expectations
Gradle conventions apply the same build policy across repositories
Platform capabilities are reused through starters, plugins, and libraries
Teams can improve the platform once and roll those improvements out more cleanly

How Helix Solves It

Helix is an ecosystem, not a single library. It gives teams a clear model for how project generation, build standards, Spring Boot integration, and reusable runtime modules fit together.

Templates

Start new services and libraries from a versioned project baseline.

Docs CLI

Generate, inspect, and manage templates from a repeatable command-line workflow.

Docs Plugins

Apply shared Gradle conventions for quality, publishing, and build behavior.

Docs Starters

Wire platform capabilities into Spring Boot applications with focused integration modules.

Docs Libraries

Reuse implementation building blocks for platform concerns across many services.

Docs

Template Engine

Create services from versioned templates that already reflect your platform structure and team conventions.

Convention Layer

Apply centralized Gradle logic for quality checks, dependency policy, and release behavior across repositories.

Runtime Modules

Use 100+ reusable building blocks to standardize development, observability, rollout patterns, and support workflows without copy-paste.

How Teams Use It

A short loop from service generation to platform-wide evolution.

01 Generate Start from a Helix template.

Teams begin with a consistent service structure and defaults instead of hand-building repository setup.

02 Build Run shared Gradle policy and checks.

Common quality gates and dependency rules are applied automatically in every project build.

03 Operate Adopt reusable runtime modules.

Services plug in standard modules for platform concerns like observability and error reporting.

04 Evolve Upgrade centrally and reduce drift.

Platform improvements roll out through shared framework updates instead of one-off repo changes.

Module Spotlight

A few examples of the kinds of platform capabilities Helix makes reusable across services. The goal is not just more modules. It is fewer one-off implementations of the same operational concerns.

`helix-metrics`

Standardized metrics integrations with Prometheus, OTLP, Datadog, and StatsD starter options.

`helix-featureflags`

Feature flag modules with LaunchDarkly, Unleash, and properties-backed options for safe rollout control.

`helix-status`

Status tracking modules with Redis-backed support to improve async workflow visibility and support operations.

`helix-shadow`

HTTP, SNS, and SQS shadow traffic modules for validating behavior safely before full production exposure.

`helix-errorreporting`

Error reporting integrations for Rollbar and Sentry with Spring Boot starter support for consistent triage.

`helix-retry`

Reusable retry primitives for resilient service calls and dependable handling of transient failures.

Browse Libraries

Under The Hood

Built for real platform workflows with 100+ reusable libraries that are ready to plug into applications and roll out consistently across repositories.

Consistent starts: template generation keeps project structure predictable from day one.
Shared enforcement: build conventions make standards automatic rather than optional.
Operational reuse: more than 100 libraries provide standardized building blocks for deployment, observability, and ongoing application support.

Documentation

Go deeper on installation, templates, CLI workflows, starters, plugins, and runtime modules in the docs.

Explore the Ecosystem

Familiar Framework. Phenomenal Platform.

Use Helix to align how Spring services are generated, validated, and evolved across your engineering organization.