Skip to main content

Blocks OS Consolidation & Platform Hardening

osAugust 26, 2026

Release Notes​

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 — Repeated failed sign-ins now trip an account lockout, and the lockout state is exposed on the Users API and surfaced in the console so administrators can see and manage locked accounts.

  • Archive roles & permissions — Roles and permissions can now be archived through dedicated endpoints and archive actions in the UI, retiring them without deleting history.

  • Role-change impact preview — Editing a role now previews the impact of the change, propagating role permission counts and confirming cross-organization effects before they are applied.

  • 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, and the data-action node can authenticate with the platform directly, 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, and workflows can integrate storage services directly.

  • 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.