New Managed AI tenant review is live Tenant-isolation security for SaaS

Stop one customer from seeing another customer's data.

BoundaryCI combines deterministic CI checks with optional managed AI review to catch dangerous Supabase and PostgreSQL authorization changes before they reach production.

$npx boundaryci scan .

Free deterministic scanner · Managed AI on paid plans · No database credentials

boundaryci / pull request #142CI
npx boundaryci scan .

Scanning 12 SQL migrations...

HIGHBND004

Authenticated policy is not tenant-scoped

Every signed-in user can read rows without checking the active organization.

supabase/migrations/004_customers.sql:17
using (true)
FIXMatch organization_id to the user's active membership.
1 high0 medium0 lowMerge blocked
Managed AIPolicy interaction reviewed
Cloud historyEvidence preserved
AVAILABLE THROUGHnpm Public packageGitHub MarketplaceOpen source CLIFinal-state migration analysis
The boundary problem

Your database can be online, encrypted, and still expose the wrong customer.

Multi-tenant SaaS depends on small authorization policies being correct everywhere. One permissive migration can quietly turn a shared database into a cross-customer breach.

01
RLS

Missing row-level security

A new table enters an exposed schema without enabling or enforcing tenant policies.

02
ANY

Policies that trust everyone

An authenticated check proves a user signed in, but never proves which tenant they belong to.

03
DEF

Privileged function bypasses

A security-definer function introduces a path around otherwise-correct access controls.

From migration to evidence

Security that lives in the pull request.

Start locally in seconds. Add Cloud when your team needs durable proof across repositories.

01LOCAL

Scan the final policy state

BoundaryCI follows migrations in order and evaluates what security actually remains.

02CI

Block dangerous regressions

GitHub annotations point to the vulnerable policy before the pull request can merge.

03CLOUD

Preserve team-wide history

Store minimized findings, usage, and remediation evidence behind tenant-safe access.

Deterministic + AI

Known failures get hard rules. Subtle policy interactions get a second review.

BoundaryCI's high-confidence deterministic checks remain the reliable merge gate. Paid teams can authorize managed Fireworks AI to examine how tenant keys, memberships, RLS policies, and privileged functions work together—without managing another provider key.

01Advisory by default02Explicit manager consent03Provider key stays server-side
tenant-review / projects.sql
DETERMINISTICMerge gate

BND004 · Authenticated policy is not tenant-scoped

Repeatable final-state rule with file evidence and remediation.

HIGH · BLOCKING
MANAGED AIAdvisory review

Membership check may not correlate to the protected row

The policy proves membership in an organization, but does not compare it with projects.organization_id.

REVIEW · HUMAN VALIDATION
Local-first by design

Your database credentials never belong in a scanner.

Deterministic scans run inside your machine or GitHub runner. Cloud history receives a minimized, secret-redacted result. Paid teams can separately authorize managed AI review, which forwards locally redacted migration text without storing it.

  • No database connection requiredAnalyze migrations without production access.
  • Cloud is opt-inLocal scans make no BoundaryCI network request.
  • Repository-bound tokensUpload credentials cannot cross repository boundaries.
  • Managed AI requires consentFireworks review activates only after an organization manager authorizes it.
Read the security model →
Your environment
SQL migrationsLocal for deterministic scans
BoundaryCI scannerDeterministic analysis
Cloud history or consented AI
BoundaryCI Cloud
Minimized findingEvidence + remediation
Tenant-safe historyHashed ingestion token
Simple pricing

Start free. Pay when BoundaryCI becomes part of how your team ships.

Annual plans include two months free. Manage plan changes and schedule cancellation through Stripe.

Free

Prove tenant isolation on your first SaaS repository.

$0USD / month
No card required
  • 100 Cloud scans per month
  • Repository-bound upload tokens
  • Scan history and finding evidence
  • Deterministic tenant-isolation checks
Start scanning free
Growth

Higher-volume assurance across a growing SaaS portfolio.

$149USD / month
$1490 USD/year when billed annually
  • 10,000 Cloud scans per month
  • Everything in Team
  • Capacity for multi-repository CI
  • Priority product support
Choose Growth

Paid subscriptions renew automatically until canceled. Cancellation normally takes effect at the end of the paid period. Charges are non-refundable except where required by law or agreed in writing. Stripe processes card information; BoundaryCI does not store complete card numbers. Review the subscription terms and privacy notice before purchase.

Enterprise

Need private runners, custom controls, or procurement support?

Talk to us
Questions, answered

What teams need to know before trusting a security check.

How do I connect a GitHub repository?+

Create the repository in BoundaryCI Cloud, store its one-time token as the GitHub Actions secret BOUNDARYCI_CLOUD_TOKEN, and commit the generated workflow YAML. The token never goes in the file, and the repository dashboard keeps the safe YAML available under Setup guide.

Can one workspace monitor multiple repositories?+

Yes. An organization owner or administrator can select Add repository in the dashboard. Each repository receives its own bound token, setup guide, and scan history, while usage is counted against the organization's shared monthly allowance.

Does BoundaryCI connect to my production database?+

No. The current scanner analyzes migration files and does not require database credentials. Active testing against disposable environments is a future, separately configured capability.

What does BoundaryCI Cloud receive?+

Cloud history receives repository and commit context, summary counts, finding metadata, and short redacted evidence and remediation snippets. Complete migration files are excluded from history. If a paid organization separately enables managed AI, up to 80,000 characters of locally redacted migration text pass transiently through BoundaryCI to Fireworks and are not stored by BoundaryCI.

Is Fireworks AI required?+

No. BoundaryCI's deterministic checks work without AI and remain the source of truth for merge decisions. Team, Growth, and Enterprise organizations can authorize BoundaryCI's managed Fireworks review without creating their own Fireworks account, then disable it by organization, repository, or workflow.

Does this replace a penetration test?+

No. BoundaryCI is a focused continuous control for tenant-isolation regressions. It complements threat modeling, code review, testing, and independent security assessments.

Can I adopt it with existing findings?+

Yes. Commit a reviewed baseline, then fail CI only when a new regression appears. Owned, expiring waivers keep temporary exceptions visible.

Protect the boundary

Your next migration should not become your next breach.

Run deterministic checks locally, then connect your repository for optional managed AI review and durable evidence.

Start free Add from Marketplace