Network Connectivity Guidelines for Trial Accounts
Thank you for exploring Digital.ai Release SaaS for enterprise orchestration!
To ensure a secure and reliable trial experience, your trial environment is hosted with specific connectivity limitations. These restrictions help protect customer data, prevent misuse, and maintain consistent performance for all trial users.
Connectivity Overview
| Capability | Trial Environment | Details |
|---|---|---|
| Outbound Internet Access | Restricted | Connections to the public internet are blocked unless to pre-approved domains required for the trial. Example: You can connect to api.github.com if it’s whitelisted, but you cannot browse arbitrary sites like example.com. |
| Approved External Services | Allowed (Whitelisted) | Certain services like GitHub, Jira, or cloud storage providers may be accessible if required for trial features. Example: You can link your trial to a public GitHub repository or Jira Cloud project, but not to an internal bug tracker. |
| Inbound Connections | Not Supported | External systems cannot directly connect to your trial environment. Inbound webhooks are only supported for approved IP ranges. Example: You cannot SSH into the trial server or send data directly from your local database. |
| Private Network Access (VPN, VPC Peering) | Not Supported | Direct connectivity to on-premises systems or private VPCs is not available in the trial. Example: You cannot establish a VPN tunnel to your corporate network to fetch internal data. |
| Third-Party Integrations | Sandbox Mode | Some integrations operate in a simulated or sandbox environment (e.g., mock S3 buckets, test payment gateways). Example: Payment gateways may run in “test mode” with fake transactions for demo purposes. |
| File System / Shell Access | Not Supported | Direct file system or shell/SSH access is not provided. Example: You cannot log into the trial server to install custom scripts or software. |
| Data & API Limits | Enforced | Outbound API calls and data transfers may be rate-limited to ensure fair usage. Example: API usage may be capped at 1,000 requests per hour. |
Why These Restrictions Exist
- Security – Protects your data and prevents exposure to untrusted networks.
- Stability – Ensures the trial runs smoothly for all participants.
- Compliance – Meets industry requirements for safe trial environments.
- Cost Management – Keeps trial usage within predictable limits.
Moving to a Paid Plan
When you upgrade to a paid subscription, you unlock:
- Full outbound internet access
- Private network connectivity (VPN, VPC peering)
- Production-level integration capabilities
- Higher API and data transfer limits
For more details, Contact Support or Accounts Team.