Franklin is a cloud-based platform that requires network connectivity for all operations. This article provides guidance on the network configuration, connectivity requirements, and integration options necessary to ensure secure and reliable access to the Franklin platform.
See also: For browser, operating system, and display requirements, refer to the Minimum Secure Operating Environment article.
Internet Connectivity Requirements
A stable, secured internet connection is required to access the Franklin platform and to support data uploads, analyses, and reporting. All communication between the user’s browser and the Franklin platform occurs over encrypted HTTPS connections.
Parameter | Requirement |
Connection Type | Stable, secured internet connection |
Protocol | HTTPS (TLS 1.2 or higher) |
Required Port | Outbound TCP port 443 (HTTPS) |
Additional Ports | No additional port configuration is required beyond standard HTTPS |
Bandwidth | Sufficient bandwidth to support genomic data file uploads and interactive platform use |
Note: Franklin does not require any inbound connections or special VPN configurations. All communication is initiated outbound from the user’s browser to the platform.
Firewall and Proxy Configuration
Organizations using firewalls, web proxies, or content filtering should ensure the following to allow uninterrupted access to the Franklin platform:
Configuration | Details |
Outbound HTTPS | Allow outbound HTTPS traffic (port 443) to Franklin platform domains |
SSL/TLS Inspection | If SSL inspection is performed, ensure that Franklin platform domains are allowlisted to prevent certificate errors or connectivity issues |
Web Proxy | If a web proxy is in use, ensure it supports HTTPS pass-through and does not block WebSocket connections used by the platform |
Content Filtering | Allowlist Franklin platform domains in any URL filtering or content categorization systems |
The operating environment shall support compliance with applicable local network security policies, including firewall, access control, and secure communication requirements.
Data Encryption in Transit
All data transmitted between the user’s browser and the Franklin platform is encrypted to protect the confidentiality and integrity of sensitive genomic and clinical information:
All user data is encrypted in transit using SSL/TLS with AES-256 encryption, both over the internet and internally within the cloud infrastructure.
The platform enforces TLS 1.2 or higher for all connections.
This encryption minimizes the risk of data interception in the event of unauthorized access to networks or communication channels.
Data Upload Connectivity
Franklin supports multiple methods for uploading genomic data files to the platform. All upload methods use encrypted connections:
Upload Method | Description |
Browser Upload | Direct file upload through the web interface for genetic data files including FASTQ, BAM, VCF, and CRAM formats |
AWS S3 Transfer | Upload from or to Amazon S3 buckets for large-scale data transfers |
BaseSpace Import | Direct import from Illumina BaseSpace for seamless integration with sequencing workflows |
Note: For large genomic datasets (e.g., whole genome sequencing), S3-based transfers are recommended to ensure reliable and efficient data delivery.
API Integration
Franklin supports API-based integration with external laboratory and clinical systems to enable automated data transfer and workflow orchestration:
Laboratory Information Management Systems (LIMS): API integration for automated sample submission, status tracking, and results retrieval.
Electronic Medical Records (EMR): Integration for clinical data exchange and reporting.
Other Data Management Systems: Custom API integrations can be configured to facilitate seamless data transfer with institutional systems.
All API communications are conducted over HTTPS using TLS 1.2 or higher, ensuring data confidentiality during transfer. API access requires authentication and is governed by the same role-based access controls applied to the platform.
See also: For API authentication procedures and access control details, refer to the Access Control and Authentication article.
Data Hosting Regions
Franklin utilizes Amazon Web Services (AWS) data centers across multiple geographic regions. Data residency is determined based on the customer’s service agreement and applicable regulatory requirements.
Region | Location |
Europe | Ireland / Frankfurt |
United States | Ohio |
Canada | Canada |
Southeast Asia | Australia |
Israel | Ireland |
Northeast Asia | Japan |
Network latency and upload performance may vary depending on the user’s geographic proximity to the assigned hosting region. Contact your account representative for region-specific connectivity guidance.
Network Environment Compliance
Organizations are responsible for ensuring that their network environment meets the connectivity requirements described in this article. This includes:
Maintaining a stable and secure internet connection in compliance with local network security policies.
Configuring firewalls and network settings to permit outbound HTTPS access (port 443) to the Franklin platform.
Ensuring that network infrastructure supports the bandwidth requirements for genomic data upload and interactive platform use.
Coordinating with IT security teams to allowlist Franklin platform domains where necessary.
Ensuring that any SSL inspection, web proxy, or content filtering systems are configured to allow uninterrupted access to the platform.
See also: For information on how Franklin behaves during connectivity loss and how data is protected during interruptions, refer to the Technical and Procedural Security and Privacy Safeguards article.