Skip to content
KeyRack

Go Services

Fit today: Good — via gRPC, REST, or AWS KMS shim (commercial).

Who

Section titled “Who”

Go backend engineers — Kubernetes operators, microservices, DevOps tooling, cloud-native infrastructure platforms.

How KeyRack serves Go today

Section titled “How KeyRack serves Go today”
Section titled “Option A: gRPC (recommended)”

Generate a Go client from KeyRack’s protobuf definitions:

Terminal window
protoc --go_out=. --go-grpc_out=. proto/keyrack/v1/key_service.proto

Option B: REST

Section titled “Option B: REST”

Standard HTTP JSON API — no code generation required.

Option C: AWS KMS shim (commercial, brownfield)

Section titled “Option C: AWS KMS shim (commercial, brownfield)”

For existing aws-sdk-go-v2 integrations, the commercial AWS KMS shim accepts the same SDK calls with a single endpoint change — see Commercial extensions.

What’s ready today

Section titled “What’s ready today”
  • Full gRPC and REST APIs
  • AWS KMS shim for brownfield migration (commercial)
  • Prometheus metrics and structured audit

What’s missing

Section titled “What’s missing”
  • Go SDK — no published go module wrapper yet. A thin SDK over gRPC (connection pooling, retry, error handling) is high-value new work.
  • Published protobuf modules on a stable import path

See Brownfield migration for FOSS adoption paths and Commercial extensions for the AWS shim.