OS is the central application and credentials management layer. Register apps, issue credentials, configure secrets, and manage projects from a single place, in the portal or from the CLI.
Register and manage applications centrally
Issue and rotate client credentials securely
Manage projects, environments, and domains
Scriptable through the Blocks CLI: sign-in, projects, secrets and scaffolding
Configure and manage tenant secrets
Client IDblocks-app-01
Secret••••••••••
IAM: Enterprise Identity & Authentication
Manage who can sign in to your apps from one console. No custom auth libraries to maintain.
Flexible sign-in: email and password, SSO and MFA
External identity systems integration (Keycloak, Okta, Azure AD)
Enterprise-grade access controls with customizable Token Lifecycle and CAPTCHA
Machine-to-machine Client Credentials and Role-based security.
Global Localization & AI Translation
Manage keys, translate, and publish to any language from one interface. No redeployment needed.
Centralized dictionary management mapped to unique UI keys and dynamic modules.
One-click AI translation for hundreds of keys across your languages.
Import and export JSON, CSV and Excel files.
Publishing updates the live app without a redeploy.
Embed LLM reasoning agents into any frontend with a single script tag. Includes Knowledge Bases, RAG, and MCP protocols.
Run sequential flows or let agents reason autonomously.
Configure your provider's model and parameters in the Blocks console.
Attach Knowledge Base documents to sharpen agent responses.
Conversation logs that show the steps, tools and sources behind each answer.
Data: GraphQL Data & File Storage
Define your schemas in the Data Gateway and get GraphQL queries and mutations for them. Connect an external database or use the managed one. Upload and download files through presigned URLs and the file APIs.
Auto-generated API Endpoints
Data Gateway
data_collections
storage_buckets
Release & Monitor
git push originDeploy
Live
Logic: Visual Workflow Automation
Drag triggers, conditions, and actions onto a canvas. Automate multi-step processes without writing code.
Build with drag-and-drop triggers, actions, and logic nodes.
Fire via standard Webhook endpoints or raw Email receipt triggers.
Automatically execute an AI Agent node to reason over dynamically injected parameters.
Push outward with built-in HTTP request, Email, and Database actions.
What a SELISE Blocks project includes, how setup and deploys work, and where it can run.
What is SELISE Blocks?
SELISE Blocks is an enterprise backend-as-a-service for web, mobile and desktop apps. Each project gets login and user management with SSO, MFA and roles, a GraphQL data layer, file storage, translations, email, notifications, workflows, deployment and monitoring. You set it up from the Blocks CLI or the web console, or paste one prompt into a coding agent such as Claude Code, Codex or Cursor and let it run the CLI for you.
How fast can I go from zero to a running application?
Paste the bootstrap prompt into your coding agent. It installs the Blocks skills, signs you in, picks or creates a project and scaffolds an app that already has hosted login. From there you add schemas, translations and workflows as you need them.
How does deployment work?
Connect your GitHub repository, map branches to environments (dev → Development, stg → Staging, main → Production), and push. SonarQube (SAST) and Dependency-Track (SCA) scan every build and attach their reports to it. Manual deployments are also available: click Deploy, select the environment, confirm.
What authentication methods does Blocks support?
Email/password with lockout policies, social login via Google, Microsoft, GitHub, LinkedIn, and X, client credentials for machine-to-machine API access, and external IdP integration with Keycloak, Okta, Azure AD, and any OIDC-compliant provider. MFA via email or authenticator app sits on top of all of these.
Does Blocks lock me into a specific cloud provider?
No. The Blocks services are open source on GitHub, and you can run them on your own infrastructure or another cloud instead of os.seliseblocks.com. There is no step-by-step self-hosting guide yet, so plan on working from the repositories. Your frontend connects to Blocks through standard APIs, so migrating off is a configuration change.
What does the built-in observability cover?
Blocks services report logs, traces and usage metrics without setup. Your own services show up after you register them and add the Blocks package for .NET, Python or Node, which uses OpenTelemetry. Uptime monitors check your endpoints and email you when one fails.
Who is Blocks built for?
Teams building enterprise web, mobile or desktop apps, B2B SaaS, or internal tools under tight timelines. It suits organizations without dedicated DevOps and teams adding AI to existing products. It is not designed for simple public-facing sites that have no enterprise security or compliance requirements.
What kind of support do I get?
Documentation at docs.seliseblocks.com, the public GitHub repository at github.com/SELISEdigitalplatforms for issues and contributions, and direct email support at support@selisegroup.com. Enterprise customers get priority operational support as part of their plan.
Is SELISE Blocks the same as AWS Blocks?
No. AWS Blocks is an open-source TypeScript framework from Amazon Web Services, released in preview in June 2026. SELISE Blocks is a separate hosted platform made by SELISE Digital Platforms.
Your next project shouldn't start with infrastructure.
Install the CLI, or paste one prompt into your coding agent and let it set up your first project.