Changelog

What's new in Blocks

New features, improvements and fixes, shipped as they land.

2026.08.26

Blocks OS Consolidation & Platform Hardening

IAMDataLogicReleaseOSUtilitiesLocalizationMonitor

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.

2026.07.30

Blocks OS Platform

OSIAMDataLocalizationLogicUtilitiesReleaseAgentsMonitorStudio

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.

v3.7.7

Advanced Health Monitoring

IAMMonitor

Health overview dashboards, service monitors and alerting in Deploy & Observe, plus new social logins and JWT claims mapping.

This release introduces powerful new authentication options, deeper health monitoring for deployed and managed services, and improved visibility into system uptime. v0.0.8 expands Deploy & Observe into a full monitoring suite while delivering more flexibility in identity mapping across external providers.

Release Notes

v3.7.7 enhances platform observability with a new Health view, configurable service monitors, and alerting options. On the Identity side, expanded social logins and JWT claim mapping streamline authentication and integration for both Blocks Cloud and Construct apps.

Authentication

New Social Logins

Users can now authenticate using GitHub, X (Twitter), and LinkedIn.
These new social login providers are supported across:

  • Blocks Cloud
  • Construct projects

This simplifies onboarding, enables broader identity federation, and reduces friction for end users.

JWT Claims Mapping

Different identity providers expose different fields inside their issued JWT tokens.
With JWT Claims Mapping, administrators can now:

  • Map external token fields to Blocks Cloud–expected fields
  • Align custom claims from third-party identity providers
  • Ensure seamless authentication flows across Construct and Cloud

All mapping is done directly through the Cloud portal for consistency and ease of configuration.

Deploy & Observe

Modern cloud platforms rely on real-time visibility, automated health checks, and proactive alerting — and Deploy & Observe continues to evolve to meet these industry standards. With v0.0.8, Blocks Cloud introduces a comprehensive health monitoring experience that brings deeper transparency, better uptime awareness, and stronger operational control across all services.

New Features

  • Health Overview Dashboard — view uptime summaries and a 24-hour health timeline, where each bar represents one hour of service health.

  • Hover & Click Insights — hover to see uptime percentage and time ranges; click to open detailed monitoring options.

  • Service Details View

    • Incident history
    • Notification configuration (email recipients, triggers, etc.)
    • Callback monitoring support (your service pings Blocks Cloud to confirm it’s alive)
    • Request-based monitoring (Blocks Cloud pings your service to verify availability)
    • Support for JSON payloads and custom headers
    • Options to pause or delete monitors

  • Core, Managed & Deployed Services Monitoring — health checks now support all service types across the platform.

  • Monitoring Setup in Deploy & Observe — configure callback or request monitors directly from the dashboard with an improved setup flow.

Benefits

  • Unified visibility — see the state of your entire ecosystem (core services, deployed workloads, and managed services) from a single view.
  • Proactive issue detection — understand uptime patterns hour-by-hour and catch incidents before they scale.
  • Fewer surprises in production — automated health checks ensure that degraded services are flagged quickly.
  • Flexible monitoring — choose callback or request-based checks depending on how your service reports health.
  • More control — pause, delete, or reconfigure monitors without redeploying anything.

Bug Fixes

  • Fixed issue where all client credential grant types were being set as inactive.
  • Resolved issue where already filled-in values were being translated when using auto-translate.
v3.7.6

Managed Services, Smarter IAM & User Docs

OSIAMDataAgentsLocalizationMonitor

Dedicated Data Gateway instances per project, external IdP and client credentials support, context-aware AI translation, and managed services.

This release focuses on isolation, identity, and intelligent communication. Each project and environment now has its own schema, ensuring complete data separation. The IAM module gains new authentication options, while the AI, Communication, and Managed Services sections see meaningful functional and usability updates.

Release Notes

v3.7.6 introduces dedicated Data Gateway instances, smarter identity management with client credential support, and context-aware AI translations. These enhancements improve security, flexibility, and collaboration across SELISE Blocks Cloud.

Projects & Environments

Every project and environment now has its own schema, replacing the previously shared model.
This provides complete isolation between environments, ensuring that project-specific data, rules, and configurations remain independent.

IAM (Identity & Access Management)

New Features

  • External IdP JWKS Support — Administrators can now integrate third-party authentication providers such as Auth0, Keycloak, or any custom OpenID Connect (OIDC)–compliant service through JWKS (JSON Web Key Set) configuration. By sharing the provider’s JWKS endpoint within IAM settings, Blocks Cloud can directly verify tokens issued by these external systems. This enhancement allows organizations to bring their existing user base into Blocks Cloud without requiring re-registration or manual synchronization. Users authenticated through their existing IdP can seamlessly access Blocks Cloud resources while benefiting from native identity, authorization, and LMT (Logs, Metrics & Tracing) capabilities. In essence, teams can now unify their external authentication ecosystem with Blocks Cloud — maintaining centralized identity management externally while still gaining full observability and policy control within the platform.
  • Client Credentials Grant — Added support for the Client Credentials OAuth 2.0 flow, enabling secure, machine-to-machine authentication. This allows backend services or applications to access APIs using client ID and secret without requiring user interaction.
  • SSO Renaming — The “Social” tab has been renamed to SSO (Single Sign-On) for clarity and alignment with industry standards.

Improvements

  • Tab Sequence Updated — The sequence of authentication tabs has been restructured for a more logical setup flow.

Data Gateway

New Features

  • Preview Section — Added a powerful preview interface allowing users to view endpoints for GraphQL databases, auto-generate Create/Read/Update/Delete (CRUD) queries, and inspect schema structure in JSON format.
  • Dedicated Instances per Project/Environment — Each project or environment now comes with its own Data Gateway instance, ensuring dedicated GraphQL resources and complete data separation.

AI

New Features

  • Custom Agent Banner — Organizations can now add branded banners to their agents. The banner appears at the top of the agent interface and supports image formats, allowing teams to display announcements, promotions, or visual identity elements.

Communication

New Features

  • Sinhala Language Added — Sinhala is now supported as part of the translation system, expanding accessibility.
  • Key-Specific Context Provision — AI translation models often produce linguistically correct results but can miss contextual nuances — especially when the same phrase or label carries different meanings depending on where it appears in the interface. With key-specific context provision, developers can now attach contextual metadata to each translation key. This additional layer of information helps the AI understand where and how the text is used — whether it’s part of a button, tooltip, message, or title — allowing translations to stay accurate not just in language, but also in intent and placement. As a result, automatic translations across the platform become more reliable, natural, and domain-aware, minimizing errors that come from one-size-fits-all translations.

Managed Services

New Features

  • Managed Services — The Managed Services capability allows users to connect their own backend services with the core features of SELISE Blocks Cloud — effectively extending the platform’s observability, identity, and data capabilities into their own systems. In this release, users can integrate Blocks’ native Logs, Metrics & Tracing (LMT) features directly into their managed services. This enables unified monitoring, debugging, and performance analysis across both internal and Blocks-hosted components. Looking ahead, this integration layer will expand beyond LMT to include additional platform services — allowing teams to view their service usage, operational health, and even vulnerability scans (via SCA, SAST, and DAST) within the same dashboard.
  • Future Enhancements — In upcoming releases, users will also be able to view service health and scan for vulnerabilities using SCA (Software Composition Analysis), SAST (Static Application Security Testing), and DAST (Dynamic Application Security Testing) integrations — bringing proactive observability and security into one place.

Documentation

  • User Docs Site Launched — The official documentation for SELISE Blocks Cloud is now live at docs.seliseblocks.com/cloud. Explore detailed guides, configuration steps, and API references.

Bug Fixes

  • Fixed UI responsiveness issues in the “Export Keys” section.
  • Updated “Reload Schema” API to dynamically load projects. (#1680)
  • Fixed agent scrolling issues on mobile devices. (#1497)
  • General responsiveness improvements across modules.
  • Fixed language data migration bug where duplicate keys were being created.
  • Resolved issue where Test Construct users were unable to log in due to a cache problem. (#1645)

Summary

SELISE Blocks Cloud v3.7.6 continues the journey toward isolation, intelligence, and integration — offering developers more control, businesses stronger identity options, and teams smarter tools for communication and observability.

v3.7.4

AI Enhancements & UILM Updates

AgentsLocalizationMonitorOS

Customizable AI agents, UILM history with recast, AI-powered logs and tracing, and environment migration.

This release introduces the Data Gateway service to Construct along with an early-stage integration of Storybook for component previews.

Release Notes

This release expands flexibility and intelligence across the platform. Users now have better control over AI Agents through customizable enhancements, user workflow tracking, and history and context retention with UILM. AI-powered Logs, Metrics & Tracing enhances environment migration starting with the UILM model. Together, these improvements make the platform more adaptable, resilient and effective for a wide range of applications.

Environment Migration

Our cloud platform now supports environment migration, giving users the flexibility to move data between environments. This capability minimizes workloads, simplifies testing, and reduces resource consumption when transferring projects. Support begins with the UILM language model. Migration ensures better traceability and logs for auditing. Migration support will gradually extend across additional models and services.

UILM

UILM now includes language history with recast capability, enabling users to track changes and restore previous versions when needed. This is especially useful for recent project introductions or errors. If you want to compare different states, or simply rewind to a prior task to enhance functionality, this major change enables safe and reversible UILM edits. Boosts safety and flexibility for your workflows.

Bug Fixes

  • Resolved issue where API calls occurred with decoupled modules in "Create New Key".
  • Fixed non-functional reset button appended with no previous data available.
  • Corrected alignment issues within the module selection field.

Logs & Tracing

Our Logs, Metrics & Tracing (LMT) now has AI support, allowing users to query logs, metrics, and traces in natural language. You can even search directly by trace ID making it easier to diagnose issues and ensure integrity.

New Features

  • Added support for searching by trace ID.
  • Enhanced Ask AI, providing descriptive insights powered by AI.

AI Agents

AI Agents now give users more control through adjustable parameters, ensuring the assistant behaves as needed – whether that means more focused, more creative, or more efficient.

New Features

  • Context window – set how many past messages are remembered.
  • Context preservation – additional summarization and conversation tools to preserve context.
  • Embeddings models:
    • Embedding v2 base: standard batch size for large models
    • Embedding v3 small
    • Embedding v3 large
  • Chunking Strategy – choose how text is split into chunks:
    • Sentence
    • Semantic
    • Windowed
    • Custom
  • LTM Conversation – added source links under each response to trace the origin of information.
  • Dialog reset – history of the conversation page has been changed.
  • The agent playground page has been redesigned.

Improvements

  • Enhanced response quality with improved retrieval re-ranking, including semantic clustering for more accurate and relevant results.
  • Changed the trace accounts with relevant focus.
  • Introduced a more robust system based on the Conversation API instead of query-based interaction for better processing and retrieval.