Deployment options

Separate application access, execution environments, and enterprise deployment requirements.

RamAIn's hosted application provides the workflow workbench, workspace controls, and run operations. Browser execution happens in a separate cloud runtime; opening the workbench on your laptop does not make the laptop the agent's computer.

Understand the product boundary

Part	User-facing responsibility	What to establish
Application	Authenticate, select a workspace, build and manage workflows	The correct environment, account, and role.
Cloud browser	Operate web applications during authoring and runs	Network reachability, remote authentication, and browser settings.
Configured desktop	Operate supported Windows applications	Available region, provisioned host, application access, and permissions.
Connected services	Supply authorized external tools or account access	The connected account, scopes, and environment.
Run evidence	Record inputs, actions, outputs, and available screenshots/replay	The audience and data-handling requirements for those records.

The browser and computer guide explains the runtime choice. Integrations explains the difference between an enabled provider and a linked account.

Connect the application and API

Use platform.ramain.ai for the application and https://api.ramain.ai/api/v1 for API requests. Workflow identifiers, credentials, connected accounts, and API keys are scoped to their organization and workspace.

For API integrations, follow the API quickstart and copy the selected workflow's generated schema from API Docs. Confirm the intended workspace, network access, and remote sign-in before arranging unattended work.

Describe an enterprise requirement concretely

When discussing a private-network or customer-managed deployment, bring a short description of the intended workflow and its operational requirements:

Which applications must the runtime reach, and are they public websites, private web applications, or native desktop apps?
Which organization and workspace should own the workflows and credentials?
Which identity providers and service accounts are required?
What data, files, screenshots, and outputs will the task handle?
Which locations, retention requirements, and model-provider constraints need agreement?
Who will manage access, investigate failed runs, and maintain the target applications?

A browser proxy selection is only one runtime setting. It is not a specification for private networking, data residency, or a customer-managed deployment. Settings describes the controls that are actually exposed in the workbench.

Establish responsibilities before operating

Agree who owns workflow changes, credentials, connected services, billing, and operational response. A workflow can need intervention after a target application changes even when the hosting service is healthy. Use Sessions and Drift to investigate that execution evidence.

Availability and deployment responsibilities are defined by the provisioned environment and agreement. Use the current security materials and discuss specific requirements with RamAIn before planning an architecture.

Older infrastructure URLs remain reachable for compatibility, but their earlier reference designs and proposed deliverables are retired as product instructions. They should not be treated as the current SaaS topology or a deployment guarantee.

Was this page helpful?