Enterprise backend infrastructure

Build on a
governed backend.

WyndBase is a low-code backend for enterprise applications. Model your business data, enforce access rules, and build with the frontend you choose.

Platform in development

Fig. 01Semantic core / Concept illustration
Typed semantic data
Granular access control
Frontend-agnostic
Deployment choice

01 The platform

Build the app.
Not the backend.

Enterprise apps share many of the same backend needs. WyndBase brings 12 building blocks into one platform, so your team can focus on the parts of the app that are unique to your business.

Data & governance

Realtime database

Query a typed semantic model with WQL and push updates to application views.

Security modeling

Define row, column, and view access with CEL rules and sharing policies.

Object storage

Keep application files alongside structured data with S3-compatible storage and caching.

Secret management

Keep credentials in an encrypted vault instead of application code.

Identity & automation

User management

Bring authentication, single sign-on, and persisted user sessions into the backend.

Workflow engine

Create triggers, webhooks, and approval flows with inbox and notification support.

Collaboration

Share presence and live updates. Multi-user editing using CRDTs is on the roadmap.

Business rules

Planned server-side formulas and rule evaluation without rebuilding the frontend.

Integrations & tools

Integrations

Connect payment and email services. A broader API proxy is planned.

App analytics

Track application events and pageviews to understand how people use your apps.

Document management

Generate documents dynamically from application data and form definitions.

Business templates

Start from reusable schema patterns for apps such as CRM and HR.

Product preview

Inside the workspace.

Explore two parts of the WyndBase workspace: the semantic model and the workflow builder. Concept mockups use sample data and do not show a live product.

Illustrated Purchase orders model with typed fields and a field inspector masking vendor email for standard users.

Semantic model

Concept mockup

Define typed fields for purchase orders and set a masking rule for a vendor email field.

Illustrated three-step purchase order workflow with a creation trigger, finance approval, and a status update with notification.

Workflow builder

Concept mockup

Route a new purchase order to finance, then update its status and notify the requester.

02 Architecture

Query the model,
not the database.

The typed semantic model sits between your applications and physical storage. WQL, the platform’s SQL-like query language, is designed to query business objects, generate client types, and push changes to application views.

  • Model business concepts. Give fields such as email and phone their own types and validation rules.
  • Enforce policy at the source. Apply row, column, and view rules, with masking and encryption at the data layer.
  • Bring your own frontend. Keep your app’s data contract separate from the underlying schema and storage.
Logical architectureWB / 02
  1. Your applicationsWeb · desktop · custom UI
  2. WyndBase semantic coreTyped model · WQL · access policies
  3. Physical data layerTransactional data · analytical cubes
One data contract between your apps and storage.
Integrated analytics

The planned analytics suite brings reporting, dashboards, and connected spreadsheets to live business data, under the same access rules as your applications.

03 Deployment

Choose where your
backend runs.

WyndBase is designed for teams whose hosting and network requirements are part of the application, not an afterthought. Explore the planned deployment models.

Managed cloud

A managed environment for teams that don’t want to run backend infrastructure.

  • Managed multi-tenant SaaS model
  • Designed for cloud-first application teams

On-premises

Run the backend in an environment your organization controls, whether that’s your own infrastructure or a private data center.

  • Customer-controlled infrastructure
  • For teams with specific hosting or data-location requirements

Air-gapped

A deployment model for isolated environments where a persistent connection to public services isn’t acceptable.

  • Designed for network isolation
  • For restricted enterprise and public-sector environments

OEM embedded

Embed the backend in your own software instead of asking customers to adopt a separate frontend or platform.

  • Backend integration for software vendors
  • Frontend remains under your control

04 The company

WyndBase GmbH i.Gr.

WyndBase is being developed for teams that need more control over business data and deployment without adopting a fixed frontend. The company is in formation, with a planned launch from Potsdam, Germany.

Official company address
Am Mühlenberg 11, 14476 Potsdam, Germany

05 Early access

What are you building?

We’re looking to speak with teams building enterprise applications with complex data, workflows, or deployment requirements.

Product in development

Inquiries aren’t open yet.

In the meantime, you can explore the proposed platform and deployment models.

Explore deployment