The platform behind Prized.

Generated code never receives a Postgres connection string or a model-provider key. Tool data calls go to Prized's authenticated SQL gateway. Model traffic goes to the LLM gateway. The sandbox receives derived credentials bound to its session or tool, not the platform secrets used behind those gateways.

That makes a leaked sandbox credential narrow by construction: it cannot be used to open an admin database connection or pivot into another tool.

Each tool is provisioned with its own schema, login role, and encrypted connection URL. The production data path opens Postgres as that role. There is no shared admin connection followed by a role switch for generated code to escape through.

The role's grants constrain access at the database engine. A separate SQL guard rejects cross-schema references, multiple statements, and statements that do not belong on the requested read or write path. Read calls also run in a read-only Postgres transaction.

Tool integration calls go through Prized's egress proxy and integration broker. The proxy authenticates the caller, binds the request to a workspace, checks the destination against the platform and workspace host allow-lists, and resolves the workspace's encrypted credential on the server side.

Generated code names an approved integration and operation; it never receives the raw credential. Reads are the default path. Writes require an enabled integration write path and a caller with write access.

Publishing validates the built output and uploads its files to S3-compatible object storage under a new version. A database transaction then inserts the version record and flips the tool's current version pointer.

The gateway serves the selected bundle at a workspace-scoped URL and proxies its API calls back through the governed data plane. Private workspace tools require a short-lived, workspace-scoped JWT; the gateway verifies the signature, workspace binding, and tool access before serving the request.

Tool creation, sharing, and database access (down to the exact SQL run) are audit-logged. Workspace administrators can review that activity in the workspace audit view.

Forking copies source and lineage into a new tool. It also provisions a new schema, role, and credential. Access-control rows and integration grants are not copied from the parent, so a teammate reconnects the fork to data they are allowed to use.