Skip to main content

Introducing Blocks OS

osJuly 30, 2026

Release Notes​

Blocks Cloud is now Blocks OS. This release re-architects the platform around a unified operating console where every service runs on its own dedicated domain, migrates all applications to the new genesis-os frontend foundation on React 19, and ships a wave of new capabilities across Identity, Storage, Payments, and Workflow. It is the largest platform update since the 3.x line and the starting point for everything that follows.

Blocks OS Platform​

The platform rename is more than branding — it reflects a re-architecture into independent, individually addressable services behind one console.

  • A unified OS console — All services are now reached through a single shell at os.seliseblocks.com, with consolidated sidebar navigation and a service switcher that filters available applications by environment.

  • A domain per service — Each capability now has its own dedicated subdomain instead of sharing one Cloud origin. Identity, Data, Workflow, Deployment, Observability, Localization, Utilities, Studio, and AI each run and scale on their own host.

  • Identity & Access, in the console — User and Organization management has moved out of the standalone IAM frontend and now lives natively inside the OS console under Identity & Access, unifying administration with the rest of the platform.

  • Environment data migration — A new migration engine moves each project's data into the per-environment architecture. Migrations are authorized, OTP-verified, and emit completion events so dependent services can react when a project finishes moving.

Identity​

Identity gains a major set of authentication and access-management capabilities alongside the console move.

  • Device Authorization flow (OAuth 2.0 / RFC 8628) — Blocks OS now supports the OAuth 2.0 Device Authorization Grant, enabling sign-in on input-constrained and headless clients (CLIs, terminals, TV apps) using a short user code.

  • Social identity linking at signup — Users can link a social identity provider to their account during signup, streamlining onboarding across providers.

  • User activation flow — A dedicated activation experience captures first and last name on the activation form, and administrators can resend activation to users who remain inactive.

  • OIDC client management — Client secrets can now be rotated for OIDC clients, identity providers can be deleted, and credential saving supports an external discovery endpoint.

  • Permission management overhaul — Dependent-permission selection is clearer and easier to reason about, built-in permissions are surfaced as read-only, permissions carry a severity, and permission groups can be created and cleared directly from the UI.

  • Stronger session control — Logging out can now revoke multiple active sessions at once.

Storage & Data​

Storage is now a full document management system, and the data layer gains query and metadata improvements.

  • Document Management System (DMS) — A new content platform with fine-grained access control: content-access administration backed by an audit trail, file version history, move and zero-copy copy, cached folder ancestry with a cycle-guarded rebuild, and access-resolved children listing with cursor pagination. An effective-policy resolver evaluates access-control entries per request.

  • Richer GraphQL queries — Queries now support logical AND / OR operators for more expressive filtering.

  • Better resource metadata & docs — Permissions and resources carry names and descriptions, and the Data service ships published API documentation.

Workflow​

  • Rename workflows — Workflows can be renamed in place, and the workflow editor gains improved state management and input-panel handling.

Payments​

Utilities introduces a complete Stripe-based payments experience.

  • Stripe payments — Hosted checkout, saved cards (save and remove), and refunds are now supported end to end. Payments record the authenticated user, and the platform reuses a shopper's existing Stripe customer at checkout.

  • Multiple providers — Payment providers can be registered and configured through the API and administered from dedicated provider pages, with provider credentials stored encrypted on the provider document and incoming events verified through Stripe webhook validation.

Localization​

  • genesis-os client — The Localization application has migrated to React 19 on the genesis-os foundation, and a new extension guide page documents the localization extension workflow.

Observability​

  • Driver updates & API exploration — The observability driver was updated across services, and Swagger is enabled for exploring the monitoring API.

Developer SDKs​

The SDK line moved to v4.0 in lockstep with the platform, unified under the genesis-os name.

  • genesis-os (React) v4.0 — @seliseblocks/genesis-react is renamed to @seliseblocks/genesis-os@4.0.0 and now requires React 19.2.8 and react-router 8. It is the shared app-shell and component foundation consumed by every service application (IAM, OS, Data, Logic, Monitor, Release, Studio, Utilities, Localization), with an environment-aware app switcher. A React 19 / react-router 8 migration guide is published. (Breaking change.)

  • Blocks Genesis (.NET) v4.0 — The .NET bootstrap SDK bumped to v4.0 alongside, adding formal versioning and analysis rulesets and picking up security updates.

  • genesis-py v0.3.1 — The Python Genesis SDK received a maintenance update.