CYPEX is CYBERTEC’s PostgreSQL Application Platform: the schema drives the API, access model, and application UI. This section gets you from a fresh deployment to a first working app. Follow the path below — first-run admin setup, then sample applications.

Info

Upgrading an existing deployment? Use the Upgrade to v2.0.0 operator guide instead of a fresh install.

After the first login, configure the administration panel: organizations, access, and the steps that lead to launching an application.

v2.0.0 is the release in which CYPEX becomes a multi-tenant PostgreSQL application platform. Tenancy is a first-class object (Organizations), isolation is enforced in the database (Row-Level Security), authorization is two-dimensional (Capabilities × Data Scope), schema exposure is explicit (Schema Access), identity can be federated (SSO Gateway), and outbound integrations are governed (allowlist, credentials, enablement, audit).

Warning

This is not a drop-in patch. v2.0.0 changes the permission and tenancy model. Read the Upgrade to v2.0.0 operator guide before planning a maintenance window, then the Upgrading to v2.0.0 technical reference for the database detail.

A CYPEX deployment can serve more than one tenant — an Organization — from the same PostgreSQL database. Isolation is enforced by Row-Level Security in the database, not by UI filtering.

Welcome to the CYPEX documentation. This section covers how to build, deploy, and manage PostgreSQL applications on CYBERTEC’s PostgreSQL Application Platform.

Stay up to date with the latest changes, new features, and bug fixes across all CYPEX versions. Browse release notes from v1.3.0 to the latest version, including detailed changelogs for each release.

This section contains detailed release notes for all CYPEX versions, documenting new features, enhancements, bug fixes, and technical improvements in each release.

Browse release notes by version (newest first):

• v2.0.0 - Latest release with multi-tenant Organizations, PostgreSQL Row-Level Security, SSO OIDC/LDAP, and governed Connectors
• v1.9.3 - Bug-fix release bridging v1.9.2 and v2.0.0
• v1.9.2 - New input elements, UI enhancements, and architectural improvements
• v1.9.1 - PDF reporting, application merging, and PostgreSQL 16 support
• v1.9.0 - Admin roles, JWT configuration, and materialized views
• v1.8.8 - GeoJSON editor, custom expression editor, and OpenShift deployment
• v1.8.7 - Workflow enhancements, security improvements, and UI updates
• v1.8.6 - Query management and PostgreSQL compatibility
• v1.8.5 - Backend refactor and workflow enhancements
• v1.8.4 - Query creation fix
• v1.8.3 - Uninstallation improvements
• v1.8.2 - Dependency update
• v1.8.1 - Query group bug fix
• v1.8.0 - PostgreSQL upgrade, query groups, and trial version
• v1.7.4 - Query management improvements and repository proxy
• v1.7.3 - External database installation and hotfixes
• v1.7.0 - Application extensions, enhanced UI, and database improvements
• v1.6.0 - Extensions store, enhanced charts, and notifications
• v1.5.0 - Workflow improvements, notifications, and custom expressions
• v1.4.1 - App migration, custom CSS, and usability improvements
• v1.3.0 - Installation on existing database and usability improvements

This page describes the multi-tenant Organizations model introduced in CYPEX v2.0.0 and why PostgreSQL Row-Level Security (RLS) is part of it.

Before v2.0.0, a CYPEX instance was effectively single-tenant:

• One database, one application schema, one set of users.
• Multi-tenancy was emulated at the application layer by filtering rows on a client identifier.
• PostgreSQL row-level security was not enabled on tenant-scoped tables.

This worked, but every enforcement decision lived in application code. A single missing WHERE clause, an ad-hoc reporting query, or a hand-written maintenance script could leak rows across tenants.

This is the hands-on companion to Connectors (the architecture reference) and the individual GUI pages under Administration panel → Integrations. It walks through building one connector end to end, using real screenshots and a real (sanitised) request/response captured while writing this guide.

Two things must exist before you can even save a connector — the order below is enforced by the backend, not just a suggested reading order:

This page is the operational counterpart to the conceptual pages in the Administration panel section. It targets operators standing up a CYPEX deployment for the first time.

For the why behind the admin IA, see the Administration panel landing and the linked per-section pages. For org / Schema Access operations specifically, see the Organizations setup guide.

Before walking through the procedures, skim the relevant admin pages:

Before you start assigning clients to organizations, walk through this preparation checklist. The procedures on this page are the same shape as the v2.0.0 pre-upgrade checklist, but focused on the post-upgrade multi-tenant setup rather than the upgrade itself.

The procedures here assume the v2.0.0 migrations have been applied. Verify:

v2.0.0 redesigns the login screen. This page describes it from the user’s side: what you see, what to type, and what the messages mean. Administrators configuring providers should start at SSO providers (OIDC) instead.

Two ways in, on one screen:

• Username / Email and Password — sign in with your CYPEX account.
• Or quick sign in: — sign in through your organization’s identity provider (Google, Microsoft Entra, and others), if one is configured.

This page is the mandatory upgrade entry point for CYPEX v2.0.0. It is written for operators who run CYPEX in production and need a single walkthrough that covers every breaking change in this release.

Audience. Read this end-to-end before opening the maintenance window. It links out to detailed pages for each topic; follow every link in the order presented.

v2.0.0 introduces seven platform-level changes. Each one is breaking or behavior-changing for at least one class of deployment.