go-kratos/kratos

Your ultimate Go microservices framework for the cloud-native era.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 1 minute ago
Added to GitGenius on September 2nd, 2026
Created on January 10th, 2019
Open Issues & Pull Requests: 112 (+0)
GitHub issues: Enabled
Number of forks: 4,179
Total Stargazers: 25,911 (+0)
Total Subscribers: 436 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 26.0 hours
Mean response time: 13.8 days
90th percentile: 30.6 days
Tracked items: 120

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 6% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 19
New in 7 days: 0
Closed in 7 days: 1
Avg open age: 153 days
Stale 30+ days: 14
Stale 90+ days: 2

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • question (65)
  • bug (52)
  • feature (21)
  • proposal (4)
  • help wanted (2)
  • docs (1)
  • good first issue (1)
  • stale (1)

Detailed Description

Kratos is a lightweight Go framework for building cloud-native microservices.

The framework addresses the complexity of microservice development by providing small, explicit APIs across transport, middleware, registry, configuration, logging, encoding, and code generation. It uses an API-first approach centered on Protobuf definitions, automatically generating HTTP and gRPC code from schemas. This allows developers to define service contracts upfront and focus implementation on business logic rather than boilerplate networking and serialization code. The transport layer unifies HTTP and gRPC under a consistent interface, while composable middleware handles cross-cutting concerns like recovery, logging, validation, tracing, metrics, and authentication.

Kratos suits teams building microservices that need both HTTP and gRPC endpoints without framework overhead. It works well for cloud-native deployments where service discovery, configuration management, and observability are requirements. The framework's pluggable components for registry, configuration, and encoding mean you can swap implementations to match your infrastructure—whether that is Kubernetes, Consul, or other platforms. The contrib ecosystem provides optional integrations for specific registries, config stores, and observability tools, letting you adopt only what you need.

The project maintains active development with consistent contributions across core framework components and the contrib ecosystem. Pull requests receive timely review and feedback. The codebase demonstrates attention to testing and code quality standards. Documentation is actively maintained alongside feature development, with examples and guides kept current with framework changes.