ARIN
ARIN is a local execution environment for persistent, sensitive, or environment-dependent workflows close to customer systems.
What this means
ARIN supports local execution patterns where work must happen near customer environments, internal services, or sensitive data boundaries.
It is not just “another cloud region.” It is a local runtime placement model.
Why it matters
Some operations cannot reliably run from a distant hosted environment:
- internal APIs are not publicly reachable
- sensitive files must remain local
- latency and environment dependencies affect execution reliability
How Subbasis handles it
ARIN is described as a local execution environment connected to governed execution contracts:
- workflows remain durable
- permissions/policy still apply
- evidence remains attached to execution events
When deployed appropriately, local operations do not require keeping a browser session open.
Example scenario
Compliance-sensitive onboarding workflow:
- local document checks run near customer systems
- approval gate verifies high-risk transitions
- connector actions execute with local policy boundaries
- evidence is captured for review history
What to configure
- local node placement and connectivity
- policy boundaries for local actions
- role permissions for local connectors
- evidence routing/retention expectations
Limits and deployment notes
- ARIN capability is deployment-dependent.
- Availability and scale characteristics depend on plan and runtime setup.
- Wording should remain cautious; do not assume universal production battle-testing claims.
Related docs
Continue with Federation.