Engineering Components: the building block of every Protokol project What a Protokol component is, how its fields, functions, workflows and access rules fit together, and where components are used across the platform.
Security Run identities: your code runs as someone you chose Every function, component and workflow on Protokol runs as an explicit run identity. How identities are chosen, who may change code, and why.
Security Secrets on Protokol: global env and component secrets How Protokol keeps API keys and passwords safe: write-only secrets in global env and components, read only by the code identities you allow.
Engineering Forge: ship your own apps, services and UI on Protokol Forge packages views, services, install scripts and permissions into one versioned app, built from a single ptkl.config.js manifest and developed locally with the ptkl toolkit.
Engineering Workforce in Kortex: playbooks that agents carry out, with people in the loop Workforce lets Kortex agents carry out playbooks on their own, with approvals, questions, feedback, rules and typed results, all startable from the dashboard, API, SDK or ptkl.
Engineering Kortex: the AI layer of your Protokol project Kortex is Protokol's built-in AI assistant: agents, knowledge bases, conversations, access and usage, plus the tools and actions that connect Forge apps and the ptkl toolkit to it.
Engineering Global Environment: project-wide configuration for your code The global environment keeps project-wide values in one place and exposes them as $globalEnv, with groups, $globalEnv.group(), and per-identity access to encrypted values.
Engineering Functions: serverless HTTP endpoints for your project Platform functions are standalone serverless HTTP endpoints scoped to a project, with typed signatures, Dev and Public versions, per-function environment variables and optional public URLs.
Engineering OAuth 2.0: let apps act on a user's behalf, with consent Register an OAuth client, run the authorization code flow with PKCE, and let users approve exactly what your app may do in their project, with Sign in with Protokol (OpenID Connect) on top.
Engineering Web apps: sites people open from Protokol and sign in to Create a web app that people open from their Protokol home screen and sign in to with their Protokol account, keep it private or publish it, and control what it can do.
Engineering Component extensions: add features to a component without touching it Extensions add namespaced fields, functions, workflows, templates and config to an existing component, can be switched off without losing data, and are how marketplace apps add features to components you already have.
Engineering Project templates: a working setup you install in one step Templates bundle components, workflows, integrations and apps into a project you install in one step, with declared permissions, a locked identity per installation and secrets that carry declarations only.