Security and isolation for real businesses

Replaces stitching isolation, secret storage and spend limits across separate vendors.

• Available Built and covered by automated tests.
• Rolling out Built and tested; a production step is still being completed.
• Coming soon Not available yet. A direction, not a date.

• A Postgres database per app

  Each app gets its own Postgres database and two login roles with privileged attributes switched off, so one app cannot open another app's database.

  Available

• Row-level security on your data tables

  Tables in your app that hold user data get Postgres row-level security, and the deploy audit blocks an app whose user-data table has it off or not forced for the table owner.

  Available

• CSRF protection

  Forge64's API refuses changes that carry no session or bearer credential, and the apps it generates reject cross-site writes to their API routes.

  Available

• Encrypted secrets

  App secrets are encrypted with AES-256-GCM using keys derived per tenant; exports and logs carry secret names, never values.

  Available

• Certificates only for approved hostnames

  Certificates are issued only for hostnames the Forge64 API approves; unknown hostnames get none.

  Available

• Hard spend caps

  Every metered resource has a hard cap per account, app and plan plus platform-wide daily ceilings that refuse the operation when reached; paid plans add an overage spend cap you set, and Free is never charged overage.

  Available

• Tamper-evident audit log

  Billing and project changes are written to a hash-chained audit log; verification detects an edited or removed entry.

  Available

• Network isolation between app containers

  Firewall rules that stop one app's container from reaching another app, the cloud metadata service or the scheduler ports.

  Rolling out

• Full security page (Trust Center)

Can one app reach another app's data?

Each app has its own Postgres database and roles, and connecting to another tenant's database is revoked. Network firewall rules between app containers are rolling out.

How are secrets stored?

Encrypted with AES-256-GCM using per-tenant derived keys. Exports and logs carry secret names only.

What stops a surprise bill?

Every metered resource has hard caps per account, app and plan plus platform-wide daily ceilings that refuse the operation; paid plans also have an overage spend cap you set.