e-volv
Docs menu

Launch SDKs

Flags ride the existing e-volv Observer client in each language: one init, one key, one transport, exposures on the same buffer. Server SDKs receive the ruleset and evaluate locally; client SDKs receive evaluated values for one context and never hold targeting rules. Until your platform’s SDK is available, use the HTTP API — it is what every SDK uses.

Server SDKs

These receive the full ruleset with a server key and evaluate synchronously — a flag check never performs I/O and never throws.

PlatformPackageInstallStatus
Node.js@e-volv/logsnpm install @e-volv/logsComing soon
Edge runtimes@e-volv/logsnpm install @e-volv/logsAvailable · 0.3.0
Pythone-volv-logspip install e-volv-logsComing soon
Gogithub.com/e-volv/logs-gogo get github.com/e-volv/logs-goAvailable · 0.2.0
Rubye-volv-logsgem install e-volv-logsAvailable · 0.1.0
Ruste-volv-logscargo add e-volv-logsAvailable · 0.1.0
Java and Kotlin (server)io.e-volv:logs-jvmimplementation("io.e-volv:logs-jvm:0.1.0")Available · 0.1.0

Client SDKs

These receive evaluated values with a client key (evk_pub_…) bound to an allowed origin or app id, cache the last values on device, and keep serving them when the control plane is unreachable.

PlatformPackageInstallStatus
Browser@e-volv/logsnpm install @e-volv/logsAvailable · 0.3.0
Androidio.e-volv:logs-androidimplementation("io.e-volv:logs-android:0.1.0")Preview · 0.1.0, not yet verified
iOS and macOSEvolveLogs.package(url: "https://github.com/e-volv/logs-swift", from: "0.1.0")Available · 0.1.0
React Native@e-volv/logs-react-nativenpm install @e-volv/logs-react-nativeComing soon
Flutterevolve_logsflutter pub add evolve_logsComing soon

A platform becomes available here only after its registry release exists and both conformance suites are green. The behaviour every SDK guarantees — the degradation ladder, the cache format, the exposure contract — is written down in the Launch SDK contract.