The app runs
without your keys.
Klego generates code it does not trust, runs it where it cannot escape, and keeps every credential server-side.
Six boundaries around every project.
Generated code is untrusted
Model output is input, not authority. Emitted file paths are sanitised before anything touches disk.
Previews run behind a gate
Each preview is its own container behind an access gate. A visit without the token returns 401, not your app.
Ownership is checked every time
Every project, version, sandbox and workflow operation is gated on the account that owns it.
Credentials stay server-side
OAuth tokens are encrypted at rest and used only by the server. Apps call a workflow; they never hold a token.
Provider keys never reach the app
Provider keys stay on the server — never written into generated files or passed to the container.
Failures are observable
Build, console and network output is captured so failures can be repaired, without exposing host internals.
The credential boundary, concretely.
A generated route handler gets a workflow path and an environment variable. That is the whole surface.
// app/api/leads/route.ts
const res = await fetch(
`${process.env.KLEGO_WORKFLOW_API_URL}` +
`/workflows/${WORKFLOW_ID}/invoke`,
{
method: 'POST',
headers: { Authorization: `Bearer ${key}` },
body: JSON.stringify({ input })
}
)
// no Salesforce SDK, no OAuth token,
// no client-side key, no direct API call
Controls built into the flow.
Not policy — behaviour the system already has.
- Preview containers drop all Linux capabilities except the one needed to write their own bind mount.
- Readiness requires a real HTTP response from the gate health path, not an open socket.
- Idle previews are stopped by heartbeat and a reaper; their caches are removed with them.
- Published apps run in separate containers with no preview auth and their own port range.
- Custom domains are only issued a certificate once DNS actually resolves to the published host.
- Server errors are recorded per project with the route, the user and a whitelisted prompt field — never the raw request body.
- Workflow scripts execute in a locked-down VM with no package, network or database escape hatch.
- Signed documents are sealed with a SHA-256 fingerprint and an append-only audit log.
CertificationsPlaceholder — none held today
Klego holds no completed audit, so none is claimed here — no SOC 2, no ISO, no badge row. Ask and we will answer a questionnaire directly.
Reserved: audit name, scope, period, report link.