Go LibrariesConfig. ORM. Logging. Hosting. Messaging. CLI. Codegen.

Production-grade building blocks for Go services — layered configuration, a real Unit of Work ORM, Serilog-style structured logging, a hosting framework, a typed messaging bus, a type-safe CLI framework, and a protoc-free protobuf generator.

Get Started with sconf

sorm

srog

sconf — layered configuration

Configuration modeled after ASP.NET Core's Microsoft.Extensions.Configuration. JSON, YAML, TOML, env vars, CLI args and Vault secrets — merged per key into a single typed struct.

Read the docs

🗄️

sorm — ORM with a real Unit of Work

Track entities, mutate plain structs, call SaveChanges once. Type-safe generated queries, relations, migrations, projections and optimistic concurrency for PostgreSQL, MySQL and SQLite.

Read the docs

📝

srog — structured logging

Serilog-style message templates on top of zerolog. Zero-allocation hot path, multi-sink fan-out, rotation, ECS and OpenTelemetry output, HTTP and gRPC integrations.

Read the docs

🧬

shost — hosting framework

Microsoft.Extensions.Hosting for Go. Ordered startup, graceful shutdown with a deadline, restart supervision, readiness gating, HTTP/cron/health adapters and OpenTelemetry — standard library only.

Read the docs

📨

smsg — typed messaging bus

MassTransit for Go. Typed consumers, envelopes with ids and headers, in-process retry with backoff, dead-lettering — over RabbitMQ, Kafka (franz-go) or fully in-memory in tests. Stdlib-only core.

Read the docs

⌨️

scmd — type-safe CLI framework

An answer to cobra's pain points, CommandLineParser-style. Commands are structs with tags, handlers get typed options, no globals or init(). Flags layer over sconf (argv > env > config > default), Value[T] tracks where a value came from, plus completion, man/Markdown docs, flag groups and localization.

Read the docs

🔌

protogen — protobuf codegen without protoc

One Go binary that generates messages, gRPC (all streaming), gRPC-gateway and OpenAPI v3 from .proto files. No protoc, no plugins. protovalidate constraints reflected into the schema, ASP.NET-style problem+json errors, per-method roles/permissions with enforcement interceptors, project scaffolding via init.

Read the docs