What is ApiHug?

ApiHug is an AI-native enterprise architecture factory. It treats protobuf as the system contract, then uses that contract to drive design, generation, review, and delivery across the stack.

What It Is

ApiHug combines four ideas into one product surface:

• contract-first API design based on protobuf
• generation for backend, metadata, and client-side artifacts
• review rules that keep handwritten code aligned with generated boundaries
• AI workflows that understand the same contract and framework rules

In practice, one contract can shape your API description, application scaffolding, integration surface, and AI-assisted delivery flow.

Why It Matters

Most API teams lose time in the gaps between design, implementation, and review. ApiHug reduces that drift by making the contract the source of truth.

That matters because it helps teams:

• keep API design and implementation synchronized
• regenerate safely without rewriting business logic
• standardize review around explicit framework rules
• expose a cleaner surface to AI tools, SDK consumers, and internal teams

How It Fits

ApiHug fits into the delivery lifecycle from design to integration:

Design

Define services, operations, messages, enums, and persistence metadata in protobuf.

Build

Generate backend scaffolding, OAS output, and other framework artifacts from the contract.

Implement

Write business logic only in the intended handwritten layers.

Review

Use ApiHug rules and workflow skills to verify that contracts and implementations still match the framework model.

Distribute

Publish versioned artifacts through existing repository infrastructure such as Maven.

FAQ

Is ApiHug free?

Yes. ApiHug can be used in commercial projects as well as internal platform work.

Is ApiHug open source?

The SDK is published to the public Maven repository. The IntelliJ plugin source is not currently published.

Why the name ApiHug?

We Build What We Love & Love What We Built

API means the contract. Hug means keeping engineers, consumers, and AI tools inside one shared system model.

Next Step

1. Start with the Quick Start
2. Continue to Skills & Rules
3. Explore the Tool Chain