What's new in Blocks

Data

Data Gateway schemas become versioned, auditable, and safe to roll back.

• Schema version history and rollback: Every published schema change is now kept as a version you can review and roll back to, so a bad edit is a one-click revert instead of a manual rebuild.

• Only published, validated snapshots go live: The gateway now serves only schema snapshots that have been published and validated, so a work-in-progress edit can no longer reach live traffic.

• Every pod stays on the latest schema: A schema publish is now announced across all Data Gateway pods over Redis, so a multi-pod deployment can't keep serving a stale schema after you change it.

• Reworked schema editor: The schema structure editor was rebuilt, with nested rule groups in the rule-set editor, enum editors that auto-focus, a unified style for field flags, and a principal selector with inline chips.

• Analytics date range and bucket size: The graph analytics page gains a date-range picker and a bucket-size control, so you can scope the window and resolution of your charts.

• Mobile layout: The schema header and playground now lay out correctly on small screens.

Workflow

Functions get faster, safer, and able to act as the caller.

• Caller token on demand: A function can now request a caller-scoped access token at run time with await ctx.blocks.getAccessToken(), so it calls Blocks services as whoever invoked it instead of holding a static credential.

• Faster functions: Warm calls are quicker, cold starts get a start-up CPU boost, and a function re-warms automatically after a restart. Deployment and invocation add artifact support and sandbox reuse.

• Credentials stay out of functions and logs: Functions refuse literal credentials, revoke their run grants when they finish, clean up leftover envelopes, and support force-delete. Secrets are never written to notifier, notification, scheduler, or workflow logs.

• Clearer editing: Workflow details show the workflow name in the breadcrumb with an actions menu, the output panel shows mock data with an indicator you can remove, and the HTTP node gains a None authentication option.

• More predictable runs: A step with any failed item now fails, so the run ends Failed rather than reporting a success it didn't earn.

Utilities

Subscriptions gain versioned plans and a full billing-email story.

• Versioned plans: A plan can now be versioned so it stays editable while subscribers are live on it, and existing subscribers keep the version they bought.

• One trial per plan: Each plan's trial is limited to one per subscriber, closing repeated-trial sign-ups.

• Emails in the recipient's language: Subscription notification emails are now sent in the recipient's language. Members are emailed when they are given or lose a seat, and billing contacts are notified on seat, plan, and cancellation changes.

• Edit capture delay in the portal: A payment provider's capture delay is now editable from the portal, so Adyen auto-capture settles on your schedule.

• Payment reliability: Stored-card charges now send the provider store, settlement reservations no longer block a cancellation, webhooks for references Blocks did not issue are acknowledged rather than erroring, and a recurring charge fails cleanly on a configuration error instead of hanging.

• Leaner reconciliation: The subscription sweep now runs only for tenants that have subscribed and skips tenants with no database, so background work scales with real usage.

• In-process PDF rendering: Template-engine PDFs now render in-process.

Identity

• One password prompt, not two: An existing active user who redeems a signup link now confirms their password and arrives already signed in, instead of being sent to the sign-in page to type it again.

• Email preferences: Admins can opt out of activation and organization-membership emails.

• Safer redirects: Redirect targets are validated before a full-page navigation, so a crafted target cannot send a user off-site.

• Console consolidated into OS: The admin and console pages that moved to Blocks OS have been removed from Identity, leaving one place to administer them.

Platform hardening

• Configurable Content-Security-Policy: Data Gateway and Observability now build their CSP from configuration instead of hard-coded values, and the OS app uses a per-browser style nonce in place of unsafe-inline, tightening the browser security posture without hand-editing headers per service.

Deployment & Observability

• Repo details: Deployment hides the Tracing and Logs buttons on the repo-details page, and Observability refines the SCA severity tiles and repo-detail styling.

Localization

• Import migration fix: An issue in the localization import migration has been fixed, so bringing localization data across lands correctly.

CLI

@seliseblocks/cli-os 0.9.0 is on npm, with 0.9.1 rolling out.

• GeoJson schema indexes (0.9.0): blocks data schema indexes list|create|delete manages Data Gateway indexes. A non-array GeoJson field gets a MongoDB 2dsphere index automatically and is reported separately as a read-only system index, and create builds custom indexes with --fields, --name, and --unique.

• Case-sensitive field types caught locally (0.9.0): data validate, data schema push, and data schema fields now reject a miscased scalar such as string or geojson and name the right spelling (String, GeoJson) before the server does.

• Safer previews and project targeting (0.9.1): new web --dry-run is now read-only and writes nothing, project selection is pinned per workspace so two terminals in different directories can't retarget each other, and a project token issued for the wrong tenant is detected and discarded instead of silently answering from the wrong tenant's data.

This release brings tenant-aware branding to Identity, richer schema and analytics controls to Data, a PDF ingestion engine and a redesigned plan catalogue to Utilities, and a major maturation of the Blocks CLI: / now at 0.5.0 with project source control built in.

Identity

• Tenant-branded OIDC — The OIDC sign-in experience is now rendered from template data and branded per tenant across every flow. Branding is served from the database with the logo delivered over a CDN, supports light and dark themes, and the old per-client branding fields have been migrated out behind a protected management API.

• Flexible activation — The activation password step is now configurable; when no password is collected, accounts activate on arrival. The signup page is served directly from the initiate endpoint with a flow=signup parameter.

• Clearer SSO failures — A refused SSO sign-in is now surfaced in a blocking modal instead of failing silently.

• Scoped tokens & filtering — Organization-scoped tokens can be minted with client credentials, and the users list can be filtered by role and organization.

Data

• Schema index management — A new Indexes tab lets you manage schema indexes directly, with the default ItemId index shown correctly and an accordion UI for index display.

• Graph Log analytics — Graph Log history and analytics can now optionally include Blocks Console operations, and impersonated tokens store their context in the activity record for a clearer audit trail.

Workflow

• Export & import — Workflows can now be exported and imported, making it easy to move automation between projects and environments.

• Mail configuration — Workflows can retrieve mail-server configuration and present a summary, and both the HTTP Request and data-action nodes can authenticate with client credentials or Blocks authentication.

Deployment

• Project source control backend — Deployment now exposes GitHub push-credential and create-repo endpoints, the backend that powers the CLI's new blocks git source-control commands.

Utilities

• PDF ingestion — A new PDF ingestion engine performs managed, in-process inspection of uploaded PDFs — readability, geometry, digital signature, and PDF/A conformance — through a per-file ingestion pipeline that reports a status verdict per file.

• Protected billing endpoints — Subscription and payment endpoints are now guarded with [ProtectedEndPoint], machine callers are identified by their client id, and subscription reads carry quantity bounds.

• Redesigned plan catalogue — The plan catalogue has a modern, animated visual design with improved presentation and accessibility.

Localization

• WordPress integration guide — A new guide page documents configuring the Localization WordPress plugin.

CLI

The CLI matured rapidly from its August debut, moving from 0.2.12 to 0.5.0.

• Project source control (blocks git) — New in 0.5.0: source control for the project's own code through the GitHub account connected in the Blocks portal — status, init, clone, connect, pull, push, and disconnect. Push credentials are fetched per command and never written to disk.

• New command families — captcha and secrets families were added, along with 18 release commands covering the full deployment surface.

• Safer edits — Save and update commands now read the current record and merge changes over it, so omitting a flag no longer wipes stored fields; an endpoint-verification tool checks every CLI route against the live service controllers.

• Reliability & help — A generated blocks help reference, a passive update check that asks before upgrading, and fail-closed native credential storage round out the release.

Developer SDKs

• genesis-os (React) v4.3.7 — Continued refinement of the shared OS app-shell and components across service applications.

• Blocks Genesis (.NET) v4.1.7 — Ongoing v4.1 line updates to the .NET bootstrap SDK.

The month after the Blocks OS launch focused on consolidating the new architecture and hardening it for production. Identity gained account-lockout and archive workflows, Storage matured its document model with soft-delete and sharing, Utilities introduced a full subscription-and-billing engine, and the Blocks CLI made its debut as a terminal control plane for the platform.

Identity

• Account lockout, phase 1 — Repeated failed sign-ins now trip an account lockout, and the lockout state is exposed on the Users API — a backend phase ahead of console surfacing for administrators.

• Archive roles & permissions — Roles and permissions can now be archived through dedicated endpoints, retiring them without deleting history. A console UI for archive actions is not yet wired up.

• Role-change impact API — A new endpoint reports the impact of a role-permission change ahead of time — add/remove counts, affected organizations, and users holding the role — for a future console preview experience.

• Organization improvements — Users can create an organization during signup, log out of all applications at once, and the my organizations view now reports the default organization and omits disabled ones. User email search also matches on a partial address.

• Device flow, wired end to end — OIDC authentication completes the Device Authorization Grant with organization-scoped tokens and improved error handling.

Storage & Data

• Soft delete & restore — Directories and files can now be soft-deleted and restored, so accidental removals are recoverable.

• Shared content — A new shared-content capability exposes files and directories that have been shared, with permission checks enforced across every file and directory operation.

• Schema validation — Schemas support required-field validation with a requiredOn property, and data policy rules now handle multiple right-hand operands against array fields for richer conditions.

• Public GraphQL endpoint — A dedicated public GraphQL URL is now part of the runtime environment configuration.

Workflow

• Blocks authorization on nodes — The HTTP Request node gained a Use Blocks Authorization option, so workflow calls carry proper credentials without manual token handling.

• Raw query mode — The data-action node adds a raw query mode and new GraphQL field support.

• Targeted notifications — User-specific notifications can be filtered by role and organization.

Deployment

• Environment variables — Deployment secrets have been reframed as environment variables, with runtime variables enabled per release for clearer configuration management.

• Monitoring in Deployment — Deployment now proxies the monitor list from the observability backend, bringing service health into the release surface.

• Deployment lifecycle — Deployments can be deleted, project deletion triggers a queued teardown of its deployments, and pipeline definitions and cluster credentials are now sourced from Key Vault.

Observability

• Pause awareness — Monitors can be paused, and paused state is shown across the monitor table and detail pages.

• Self-served inventory — The repository list is now served from the observability service's own API, and new monitors default their timeouts to 30 seconds.

Utilities

• Subscriptions & billing — Utilities introduces a subscription and billing engine: it issues its own invoices and credit notes, supports calendar-aligned monthly billing with a prorated first period, automatic per-price discounts, and configurable inclusive or exclusive tax per price. A resilient scheduler drives renewals and usage charges, publishes metrics, audits abandoned work, and lets operators requeue or abandon dead-lettered jobs.

Localization

• Faster key editing — Keys support inline editing and bulk editing, language tables offer copyable snippets for language, key-name and module-name values, and module tables are paginated.

CLI

• Introducing the Blocks CLI — @seliseblocks/cli-os debuts as the terminal and automation control plane for Blocks OS. It signs in through OIDC device login with OS-native credential storage, scaffolds new projects, and exposes command families for Identity, Data, Mail, Notification, Localization, Storage, MFA, and Deployment — so the platform can be operated from a terminal or an agent instead of ad-hoc API calls. A set of AI workflow skills ships alongside to guide agents through supported Blocks workflows.

Developer SDKs

• genesis-os (React) v4.2.x — The shared app-shell continued to refine the OS console experience across service applications.

• Blocks Genesis (.NET) v4.0.x → v4.1.x — The .NET bootstrap SDK moved through the v4.1 line with configuration and security updates.

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 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/blocks-kit 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.