Build, connect, deploy

An Intropy integration reaches production by keeping the Component unchanged and making its surroundings more real.

Stage	What changes	Proof
Build	You write and test the Component locally. Ports resolve to folders. Services resolve to mocks.	Unit tests, integration tests, and a local run.
Connect	The same image runs with real adapters and real platform services.	A manual test proves the wiring.
Deploy	The image is pinned as an immutable release in an environment.	End-to-end tests pass in staging.
Promote	The same digests move to the next environment.	Production runs the exact artifact staging proved.

The Component does not learn about SFTP, credentials, namespaces, brokers, or schedules during build. It knows Port and Service names. Each environment decides what those names resolve to. The resolution happens in the Dapr sidecar every Component runs with; the Dapr page names what carries the split.

That is why the tutorials use folders first. A folder proves the transformation without waiting for another team’s endpoint, firewall rule, or test account.

Where this appears

• Quick start shows build with generated sample logic.
• Transactional integration shows build with code you write.
• Local cluster shows connect on a local Kubernetes cluster.