Outbound by design
The agent establishes its connection outward, reducing the need to expose an inbound application listener solely for SchemAlign connectivity.
SchemaDock
Reach private systems without putting them on the public internet.
SchemaDock is SchemAlign's private-network connectivity agent. It provides a governed route for supported outbound pipeline connections that need to reach approved services inside a customer-controlled network.
Customer-controlled agent
Outbound connectivity
Governed destinations
Fail-closed routing
SchemAlign
Pipeline
→
Private connection route
SchemaDock
→
Approved destination
Private service
Private connectivity
A connection path for services that should remain private.
SchemaDock is designed for supported integrations that need a route into private customer networks without making the destination itself internet-facing.
Explicit connection routes
Supported outbound nodes can use a Direct or SchemaDock route according to the integration's configured connection path.
Governed destinations
Administrators can control where a SchemaDock is permitted to connect instead of treating the agent as unrestricted network access.
Controlled routing
Private connectivity should fail closed.
When a workflow is configured to use SchemaDock, SchemAlign does not silently fall back to a Direct route if the private route is unavailable. That keeps routing behavior explicit and reviewable.
SchemaDock destination policy can also be kept restrictive so the agent is limited to approved network targets.
Designed around clear boundaries
- Organization-owned SchemaDock enrollment
- Administrative enablement and routing control
- Destination Allow/Deny policy
- No silent Direct fallback
- Windows service and Linux service deployment paths
Where it applies
Use SchemaDock for supported outbound connectivity.
SchemaDock is a connection-route capability for supported Source and Destination integration traffic. Internal transformation work remains inside SchemAlign.
Keep the architecture clear
Use private routing where the connection actually crosses the boundary.
SchemAlign keeps internal transformation steps separate from customer-network routing. SchemaDock is used where a supported integration connection needs to cross into a private network, not as a transport for internal SchemAlign processing.