Feature · Go Runtime Adapter (P3)
Labels: enhancement, help-wanted
Assignee: @contexa73
Type: Feature
Parent: #1 (Roadmap 2027) · Phase 3 — 2028 H2 baseline
Position in the roadmap
Go is the third runtime expansion. The roadmap order reflects deployment volume in the targets we hear most often:
2027 → Node.js (P1, current focus)
2028 H1 → Python SDK (#03)
2028 H2 → Go Runtime Adapter (this issue)
The gRPC interceptor work materially raises Go's complexity compared to the other two adapters, which is a second reason it sits last in the sequence — not a statement on Go's importance.
Goal
Bring the Post-Authentication Runtime Control Plane to the Go ecosystem (~8 M developers, dominant in cloud-native / Kubernetes / service mesh).
Scope
| Surface |
Status |
Notes |
net/http middleware |
TODO |
Standard library baseline |
gin middleware |
TODO |
Most popular Go web framework |
echo middleware |
TODO |
Second most popular |
chi middleware |
TODO |
Composable routing |
gRPC unary interceptor |
TODO |
Server-side decision evaluation |
gRPC streaming interceptor |
TODO |
Long-running stream protection |
| OAuth2 / JWT bridge |
TODO |
Compatible with mcp-auth-server |
| Evidence sealing |
TODO |
SHA-256 8-section package |
Why Go matters for Contexa
- Cloud-native default for sidecars, service meshes, API gateways
- Strong stdlib
net/http makes adapter authoring straightforward
- Goroutine model fits well with the asynchronous evidence forwarding
Acceptance criteria
How to contribute
Reply with your Go stack (gin / echo / chi / fiber / standard library) and whether you want to take on the gRPC interceptor work — that is the surface where we most need experienced Go contributors. Early Go prototyping is welcome even before Phase 3 starts.
Reference
Feature · Go Runtime Adapter (P3)
Labels:
enhancement,help-wantedAssignee: @contexa73
Type: Feature
Parent: #1 (Roadmap 2027) · Phase 3 — 2028 H2 baseline
Position in the roadmap
Go is the third runtime expansion. The roadmap order reflects deployment volume in the targets we hear most often:
The gRPC interceptor work materially raises Go's complexity compared to the other two adapters, which is a second reason it sits last in the sequence — not a statement on Go's importance.
Goal
Bring the Post-Authentication Runtime Control Plane to the Go ecosystem (~8 M developers, dominant in cloud-native / Kubernetes / service mesh).
Scope
net/httpmiddlewareginmiddlewareechomiddlewarechimiddlewaregRPCunary interceptorgRPCstreaming interceptormcp-auth-serverWhy Go matters for Contexa
net/httpmakes adapter authoring straightforwardAcceptance criteria
github.com/contexa-security/contexa-go(TBD)go test -race)How to contribute
Reply with your Go stack (gin / echo / chi / fiber / standard library) and whether you want to take on the gRPC interceptor work — that is the surface where we most need experienced Go contributors. Early Go prototyping is welcome even before Phase 3 starts.
Reference
spring-boot-starter-contexaZeroTrustActionenum