Networking
Networking requirements depend on how RI Platform is deployed and how customer systems connect to the platform.
For most hosted platform users, networking requirements are minimal. Users access the platform through a browser, and integrations connect to approved Reliable Insights endpoints.
Network access model
RI Platform networking usually involves three main paths:
- User access - Users access the Reliable Insights Platform through a web browser.
- Pipeline datasource access - Pipeline connects to approved customer datasources to retrieve data for scheduled workflows.
- RI Connect API access - External systems, scripts, or applications connect to the RI Connect API to ingest data or use supported API workflows.
Customers should confirm that these network paths are allowed before using the platform for production workflows.
Secure networking practices
Reliable Insights recommends a security-first approach to networking.
Recommended practices include:
- Allow only the network paths required for the platform workflow.
- Use secure protocols where available.
- Avoid embedding credentials in URLs.
- Use dedicated service accounts for datasource integrations.
- Restrict datasource accounts to the minimum permissions required.
- Keep test and production datasources separate where possible.
- Review firewall, proxy, and allowlist rules regularly.
- Remove unused datasource, API, or network access when it is no longer needed.
These practices help reduce unnecessary exposure while still allowing RI Platform to connect to the systems required for customer workflows.
Hosted platform networking
For the hosted Reliable Insights Platform, customers typically do not need to manage the underlying platform network.
Customers should ensure that:
- Users can access the Reliable Insights Platform from approved networks and browsers.
- API clients can reach the RI Connect API where required.
- Customer datasources can be reached by RI Platform where Pipeline ingestion is used.
- Any required firewall or allowlist rules are approved before production use.
If a datasource is protected by firewall rules or IP allowlisting, customers can contact Reliable Insights to confirm the supported configuration.
Pipeline datasource access
Pipeline needs network access to configured datasources so that it can retrieve time-series data on schedule.
Depending on the datasource and customer environment, customers may need to allow access to:
- Secure file transfer sources, such as FTPS or SFTP servers.
- Customer SQL servers or database endpoints approved for Pipeline ingestion.
- API-based datasource endpoints.
- Required ports for the chosen datasource type.
- Required hostnames or IP addresses.
Exact datasource connectivity requirements may vary by customer, datasource type, network configuration, and agreed implementation approach.
If Pipeline cannot reach the datasource, connection tests and scheduled pulls will fail.
Customers should confirm that datasource endpoints are reachable by RI Platform and that the datasource exposes only the files, tables, paths, or endpoints required for the workflow.
RI Connect ingestion API
RI Connect allows approved external systems to interact with the platform through API workflows.
API access is authenticated using API keys. Customers should store API keys securely and only allow API access from approved systems.
For more information, see RBAC & Permissions and RI Connect API Keys.
How this supports secure administration
Clear networking setup helps customers use RI Platform securely by:
- Ensuring users can access the platform through approved network paths.
- Allowing Pipeline to ingest data from approved datasources.
- Allowing RI Connect API clients to reach the correct ingestion endpoints.
- Reducing unnecessary exposure of internal systems.
- Helping customer IT teams control firewall, proxy, and allowlist changes.
- Supporting separation between test and production workflows.
A clear networking plan helps ensure RI Platform can connect to the systems it needs while remaining aligned with customer network security policies.