VibeAudits x Cygnal

Case Study: How VibeAudits Secured and Stabilized Cygnal's Multi-Tenant Client Portal

Overview

Cygnal builds predictive models for elections, producing scores and tags that help clients understand and segment the electorate.

VibeAudits took over and audited the Cygnal Client Portal, an application built by one of Cygnal's employees to deliver those model outputs to clients.

The portal had established the core client workflow, but the inherited codebase contained issues affecting deployment reliability, transactional correctness, workspace governance, and access to sensitive audience data.

We reviewed the codebase, prioritized the highest-risk problems, and worked directly in the application to make the portal more secure, stable, and maintainable.

About the Client Portal

The Cygnal Client Portal replaced a Power BI workflow that could not meet the product's needs at scale.

Through the portal, clients can sign in, view predictive model outputs, and export voter lists containing between 30,000 and more than 3 million records per project.

The application was originally built and hosted using Replit, with Snowflake, Neon, and Clerk supporting its data, application, and identity layers.

Because the portal serves multiple client workspaces, its security depends on strict tenant isolation. Users must be able to access the audiences assigned to their workspace while every unauthorized cross-workspace request is rejected.

Its operational reliability also depends on consistent workspace creation, protected administrative access, valid report configurations, and predictable deployments.

The Challenge

The portal's core functionality was in place, but several implementation gaps created unnecessary security and operational risk:

• Build output and application startup settings were misaligned
• Environment variables were not initialized consistently during server startup
• Workspace creation could leave members or settings in a partially configured state
• Admin and workspace-creation routes needed stricter authorization
• Audience access paths needed stronger workspace-membership checks
• Audience comparisons did not consistently verify access to both selected audiences
• The final administrator of a workspace could be removed or demoted
• Report-builder users could continue without completing required selections
• Report-template updates could leave the active state inconsistent
• The Drizzle schema and migration files had drifted out of sync
• Sensitive workspace-admin behavior lacked regression-test coverage

Individually, each issue was fixable. Together, they affected the portal's ability to protect tenant data, preserve workspace governance, and behave predictably in production.

Our Engagement

Phase 1: Codebase takeover and focused audit

We began by reviewing the inherited codebase and the way the portal was built and deployed.

This phase included tracing admin and workspace routes against the intended permission model, checking how audience access was scoped, examining multi-step database operations, validating the build and startup path, and comparing the database schema with its migration history.

The audit gave the Cygnal team a clear view of which problems affected security, which threatened data integrity, and which made deployment or continued development unreliable.

Phase 2: Hands-on stabilization and hardening

Once the findings were prioritized, we moved directly into remediation.

We fixed the affected code paths, introduced safer transactional behavior, strengthened tenant and admin protections, stabilized the deployment process, and added tests around security-sensitive routes.

The first phase of the handover covered 12 commits across 15 files.

What We Fixed

1. Made Builds and Deployments Reproducible

The generated server output did not align with the package startup entry point. This meant an apparently successful build could still fail when the application started in its deployment environment.

We aligned the build output with the runtime entry point, added a Dockerfile, and standardized environment loading in the server bootstrap.

This gave the portal a predictable startup path and a repeatable deployment configuration.

2. Made Workspace Creation Atomic

Creating a workspace required several related records, including the workspace itself, its initial member, and its settings.

Previously, a failure partway through the process could leave the workspace only partially configured. We moved the operation into a database transaction so all required records are created together or none are created.

This protected data integrity and made workspace provisioning more dependable.

3. Hardened Admin and Workspace Routes

We tightened authorization around admin-only behavior and workspace creation.

Sensitive operations are now enforced by the server rather than depending on frontend restrictions. This reduced the risk of unauthorized workspace actions and privilege escalation.

4. Enforced Tenant Boundaries for Audience Data

Every audience request in a multi-tenant application must be scoped to a workspace the current user is permitted to access.

We strengthened membership checks across audience list, detail, and comparison paths. Audience comparisons now verify that the current user can access both selected audiences before returning data.

This reduced the risk of IDOR-style exposure, where changing an identifier in a request could reveal records belonging to another workspace.

5. Protected the Last Workspace Administrator

The existing role-management flow allowed the final administrator of a workspace to be removed or demoted.

That could leave a workspace without anyone able to manage users, permissions, or recovery actions. We added safeguards that prevent the change when the affected user is the last remaining administrator.

This preserved administrative continuity and workspace governance.

6. Strengthened Report and Template Workflows

The report builder allowed users to continue without completing required table and join selections.

We added validation that prevents progression until all mandatory information has been supplied, stopping invalid report configurations before they reach later stages.

We also made report-template changes safer. Replacing an active template required retiring the current version and creating a new one. We updated the flow so the related changes succeed or fail together. If the replacement cannot be created, the existing template remains active.

7. Aligned the Database Schema and Migrations

The Drizzle schema and migration files no longer represented the same database structure.

We corrected the mismatch so the declared schema and migration history were synchronized. This reduced deployment risk and made future database changes safer to manage.

8. Added Regression Tests for Authorization Rules

Security fixes are only durable when future changes cannot silently undo them.

We added automated tests around workspace-admin routes and other sensitive authorization behavior. These tests help prevent regressions in admin protection and workspace access controls as the portal evolves.

9. Fixed a Broken Dashboard Action

The Add button in the dashboard's Recent Models section did not take users to the expected workflow.

We corrected the action so it opens the New Model page directly, removing friction from a common product journey.

The Outcome

By the end of this phase, the Cygnal Client Portal had a more stable deployment path and stronger protection around its multi-tenant workflows.

VibeAudits helped the team:

• Make builds and application startup reproducible
• Standardize server environment initialization
• Make workspace creation atomic
• Restrict admin and workspace operations appropriately
• Enforce workspace membership across audience access paths
• Prevent unauthorized cross-workspace audience comparisons
• Protect workspaces from losing their final administrator
• Validate required report-builder inputs
• Make report-template updates transactionally safe
• Synchronize the Drizzle schema and migration history
• Add regression tests around authorization-sensitive routes
• Correct a broken dashboard action in the model-creation workflow

The portal now starts predictably, provisions workspaces transactionally, rejects unauthorized cross-workspace audience access, and protects administrative continuity.

This was more than a code cleanup exercise. It was a security and stabilization engagement focused on helping an important client-facing product operate reliably with sensitive analytical data at scale.

Why This Case Matters

Multi-tenant applications depend on more than working screens and successful requests. They need consistent authorization, reliable state changes, protected administrative access, and deployment behavior that can be reproduced outside the original development environment.

Small implementation gaps can otherwise have serious consequences:

• A missing membership check can expose another tenant's data
• A partial workspace setup can create inconsistent permissions and application state
• An unsafe role change can leave a workspace without an administrator
• A schema mismatch can break deployment or invalidate application assumptions
• A fragile build process can make reliable handover and operation difficult

The Cygnal Client Portal is a clear example of how focused auditing and hands-on remediation can strengthen an important client-facing product.

What VibeAudits Brought to the Project

VibeAudits combined security review, codebase takeover, and hands-on engineering stabilization.

That meant helping the Cygnal Client Portal across three levels at once:

1. Focused codebase review: Reviewing the inherited portal, its deployment path, multi-tenant access controls, workspace operations, and database consistency.
2. Direct technical remediation: Fixing authorization gaps, transactional-integrity problems, validation failures, schema drift, build instability, and broken product behavior.
3. Safer handover and continued development: Adding reproducible deployment configuration and regression tests so the portal could be operated and extended with greater confidence.

Final Takeaway

The Cygnal Client Portal delivered valuable predictive voter analytics through a dedicated client workspace. What it needed was a more secure and dependable technical foundation after its codebase handover.

VibeAudits audited the product's highest-risk paths, corrected the security and data-integrity issues we found, stabilized its deployment process, and added safeguards against future regressions.

The result was a more dependable portal and a stronger foundation for delivering predictive voter analytics securely at scale.

About VibeAudits

VibeAudits helps teams harden vibe-coded, AI-assisted, and inherited applications before hidden issues become expensive production problems.

We audit, stress-test, and improve modern applications across security, authorization, performance, reliability, architecture, edge cases, and other business-critical behavior.

If your product was built quickly or handed over without a complete security review, we help make sure it is ready for the real world.