Skip to main content
Configuration in Phinite spans several surfaces. Each layer applies at a different stage of Design → Save → Build → Deploy.

Env. variables

DEV / UAT / PROD secrets and runtime config.

Integrations

Channels, triggers, and predefined tool connections.

Build export

Pin tools, MCP, and env into immutable builds.

Model keys

BYOK provider keys for LLM, STT, and TTS.

​
Configuration layers

​
Where in the product

Graph Studio with node drawer open

Graph Studio node drawer — prompt, tools, RAG, and variables

​
Typical order

  1. Configure nodes in Studio — see Graph Studio (nodes, variables, RAG).
  2. Set Env. variables for DEV / UAT / PROD.
  3. Connect Integrations (channels, triggers, predefined tools).
  4. Save the graph, then Build — pin versions; optionally export config to build.
  5. Deploy or Expose as A2A.
Save persists the draft graph. Build freezes graph + tool versions — env variables and integration configs are resolved at runtime per environment, not baked into the graph JSON.

​
Layer details

​
Node config (Graph Studio)

See Graph Studio — Agent configuration for drawer documentation.

​
Environment variables

Store API keys, database URLs, and feature flags per environment. Tools reference env variable names — values differ between DEV, UAT, and PROD without code changes. See Env. variables.

​
Integrations

See Integrations and Integrations Hub.

​
Build export

When you Build or Expose as A2A, Phinite pins tool versions and optionally exports MCP connections and env bindings into the immutable artifact. See Build export.
Configure integrations in DEV first, validate with Test and observability logs, then promote builds to UAT and PROD.