Skip to content
NanoFlags
Start free

Changelog

What shipped,and when.

Dated entries, newest first, written from our release history. We list only what is live, and never backdate.

@nanoflags/sdk on npm (opens in a new tab)Status

November 2026

    1. LaunchSDKnanoflags 0.1.0 (PyPI)

      Python SDK 0.1.0

      • Install with pip install nanoflags (Python 3.9 or newer), or pip install "nanoflags[openfeature]" for the OpenFeature provider.
      • Flags are evaluated locally and synchronously: bool_variation, string_variation, number_variation and json_variation, each with a _detail variant that returns the reason, the matched rule and the trace.
      • Live updates over the edge's WebSocket, with on_change listeners and an asyncio wrapper (nanoflags.aio.AsyncNanoFlags).
      • Signatures are verified by default on the hosted edge; the last good configuration stays in use through failures, with an optional file cache and bootstrap.
      • Tested against the same 21,998 shared evaluation cases as the other SDKs: results are identical in JavaScript, Python and Go.
      Read more
    2. LaunchSDKIntegrationsGo SDK v0.1.0Go OpenFeature provider v0.1.0

      Go SDK 0.1.0 and the OpenFeature Go provider

      • go get github.com/motazalmaroai/nanoflags-sdk/go (Go 1.22 or newer).
      • BoolVariation, StringVariation, Float64Variation and JSONVariation evaluate locally without I/O; the Detail variants return the reason, the matched rule and the trace.
      • Live updates with OnChange, WaitForReady(ctx) for start-up, and Close() for a clean shutdown. Safe for concurrent use.
      • Signatures are verified by default on the hosted edge; the last good configuration stays in use, with an optional file store and bootstrap.
      • The OpenFeature provider is a separate module, github.com/motazalmaroai/nanoflags-sdk/go/ofprovider, so the SDK itself does not depend on OpenFeature.
      • Tested against the shared evaluation fixtures plus extra Go cases, with results identical to the JavaScript and Python SDKs.
      Read more
    3. Integrations

      Any language through OpenFeature (OFREP)

      • The edge implements the OpenFeature Remote Evaluation Protocol, so any OpenFeature OFREP provider can read your flags with an SDK key.
      • Official OFREP providers exist for Java, .NET, PHP, Ruby, Swift, Kotlin and other languages, so teams using them can use NanoFlags today.
      • Results come from the same evaluation engine as the SDKs, against your environment's current published, signed revision.
      Read more
    4. Integrations

      Management API v1, with an OpenAPI description

      • A versioned REST API for CI pipelines, scripts and infrastructure tooling: projects, environments, flags, segments, changes, publishing, revisions, scenarios, the audit log and SDK keys.
      • It follows the same rules as the dashboard: roles, independent approvals, scenario checks and protected environments.
      • Scoped API tokens with an expiry; every use is recorded in the audit log.
      • The machine-readable OpenAPI 3.1 document is served at /api/v1/openapi.json, and the reference is rendered from it.
      Read more
    5. Dashboard

      The dashboard in Arabic

      • The dashboard, sign-in and onboarding are now available in Arabic, right to left.
      • Choose the language from the user menu or your profile; it follows you to other devices.
      • Code, flag keys and exports stay in English.
    6. Website

      New site motion

      • Sections, diagrams and code samples now animate in as you scroll, and the delivery path shows a change travelling to your SDKs.
      • Motion runs only on screen and stops entirely when your system asks for reduced motion.
      • Light and dark themes, in English and Arabic.
      Read more
    7. Integrations

      GitHub App: flag states in pull requests

      • Install the NanoFlags GitHub App and link a repository to a project from the dashboard.
      • Pushes update code references, so each flag page shows where the flag is used in your code.
      • Pull requests get one comment, kept up to date, with the states of the flags they touch.
      • A "NanoFlags scenarios" check runs your saved scenarios on each pull request (Team plan and above).
      • Flag pages hint at flags that look stale, so you can clean them up.
      Read more

    1. Operations

      Hourly backups and public incidents

      • Backups now run every hour instead of nightly, and are kept for 30 days in separate storage.
      • We are alerted when the newest backup is more than three hours old.
      • The status page lists incidents and planned maintenance, with updates until they are resolved, and keeps 90 days of history.
      • Services are checked every 5 minutes, with alerts on failure and recovery.
      Read more
    2. DashboardCLI@nanoflags/cli 0.2.0

      Stricter scenario evidence, promotion records and CLI 0.2.0

      • Scenario runs by the change's author or its draft editors no longer satisfy a required scenario check: someone else has to run them.
      • Promoting a change from Staging to Production now leaves a record.
      • Scenarios are now versioned.
      • Restoring a revision to a draft now restores its segments too.
      • CLI 0.2.0 adds nanoflags flags create.
      • A setup checklist and a step-by-step quickstart in the dashboard.
      Read more
    3. SDKSecurity@nanoflags/sdk 0.4.0

      SDK 0.4.0 verifies signatures by default

      • SDK 0.4.0 verifies the Ed25519 signature of every configuration bundle by default when it talks to the official edge.
      • Signing keys can be rotated: the public key list is at edge.nanoflags.io/v1/keys.
      • Bundles carry the evaluation engine version, and an SDK refuses a bundle it doesn't understand.
      • Browser keys now receive only the segments their client-exposed flags use.
      • Deleting an environment removes its configuration from the edge.
      Read more
    4. SecurityDashboard

      Security hardening

      • The database itself now refuses an approval from the change's own author.
      • Flag values are validated against their JSON Schema before they can be saved.
      • Two-step sign-in is enforced on the server, with recovery codes.
      • Plan limits are enforced in the database, and only an owner can relax a protected environment's publishing policy.
      • Invitations need the invitee's consent and arrive by e-mail; more actions are recorded in the audit log.
      • Test sessions are off in Production.
      • The status page shows only real, live checks. Global search (Cmd/Ctrl+K) in the dashboard.
      Read more
    5. SDK@nanoflags/sdk@nanoflags/cli@nanoflags/openfeature-provider

      Client packages are public and on npm

      • The SDK, CLI and OpenFeature provider are published to npm from a public repository.
      • They are licensed Apache-2.0. The dashboard, edge and backend stay proprietary.
      • The GitHub Action lives in the same public repository.
      Read more (opens in a new tab)

    1. Launch

      NanoFlags launches on nanoflags.io

      • The dashboard and edge API are live: flags, segments, environments, drafts, change requests with approvals, scenarios, revisions and restore.
      • Every publish produces a signed bundle that reaches connected SDKs over WebSockets.
      • Propagation is measured every 5 minutes from several regions and published on the status page.
      • Paid plans through Paddle, our merchant of record, with a 14-day refund.
      • Documentation in English, and a guide in Arabic.
      Read more