The Confidence flag resolver implemented in Rust, local-resolve OpenFeature Providers and edge-compatible resolver runnables.
The tools and SDKs published for direct usage:
confidence-cloudflare-resolver: Confidence resolver service as a Cloudflare Worker (readme here)openfeature-provider: The OpenFeature providers for flag resolving
Underlying building blocks:
confidence-resolver: Core resolver cratewasmandwasm-msg: WASM resolver with communication contract towards the hosting environmentdata: Sample local development data (e.g., resolver state)
# With Docker (reproducible, no setup needed)
docker build . # Build, test, lint everythingWithout docker, the building is managed via Makefile:
make # Same, using Makefile
# E2E tests require Confidence credentials passed as Docker secret
# Create openfeature-provider/js/.env.test with your credentials, then:
docker build \
--secret id=js_e2e_test_env,src=openfeature-provider/js/.env.test \
.
# With local tools (fast iteration)
make test # Run tests
make lint # Run linting
make build # Build WASM
# Build the Cloudflare-compatible resolver (WASM):
make cloudflare
Small local benchmarks exist for Go and Node.js to validate end-to-end wiring. They are a work-in-progress and do not produce meaningful or representative performance numbers yet.
Run with Docker (streams all logs, cleans up containers afterward):
# Go benchmark
make go-bench
# Node.js benchmark
make js-benchNotes:
- Each target starts a dedicated mock server container and a one-shot bench container, then tears everything down.
- Use
docker compose up ... go-benchor... js-benchto run them individually without Make.
See LICENSE for details.