CYPEX allows superusers to make immediate changes. The edit-mode is only accessible to superusers.
However, in some cases you might want to change the application without actually using it immediately. To achieve live editing without harming productive users currently working with the application, you’ll need to use release management. Before we dig into that, it’s worth pointing out that CYPEX actually allows you to revert to a previous version of your application.
Export/Import packages CYPEX applications into portable ZIP archives for migration, backup, and deployment across instances. A package is the practical promote path: export from one environment, import into another, and get a working deployment that includes UI definitions, queries, workflows, functions, files, reports, users, roles, and optional audit logs — in structured JSON.
For governance and compliance reviews, pair packaging with the audit surfaces below: row history lives in cypex.t_history (History Tracking), table/login audit in the admin Audit section, and permission decisions in Governance evidence (cypex_log.t_permission_audit_log).
CYPEX allows multiple developers to work on different applications for the same user Role to avoid conflicts in collaborative development. Since each application is tied to a specific role with access to particular database queries, developers can build separate applications independently.
The Merge Applications feature enables developers/administrators to combine multiple applications built for the same Role into a single, unified application. This process merges all app definitions and concatenates pages, reports, and menu items, ensuring that the final merged application includes all elements from the individual applications.
Operator-facing upgrade guides, one per major version. Start here before deploying a new major version of CYPEX in production.
This section contains upgrade guides for CYPEX administrators, DBAs, and operations engineers. Use these guides when moving an existing CYPEX deployment from one major version to the next, especially when the upgrade involves schema or permission-model changes.
From v2.0.0 onward, multi-tenant isolation is a database property: PostgreSQL Row-Level Security (RLS) scopes every query. Application-layer filters are not the security boundary.
The guides are written with factual upgrade behavior in mind: what the migrations actually do, what is additive, what is breaking, what is behavior-changing, and what the rollback constraints are.
