On-Prem Setup
Fused offers an on-premise deployment option for enterprise customers who need to keep data behind their own firewall. An on-prem deployment gives you the full Fused platform — Workbench, the Python SDK, HTTPS endpoints, and serverless UDF execution — running entirely inside your AWS account.
Benefits
| Benefit | Details |
|---|---|
| Unlimited compute & storage | Scale EC2 and S3 resources to match your workloads without per-seat or per-run caps. |
| Data sovereignty | Data never leaves your VPC. Meet internal compliance, HIPAA, SOC 2, or other regulatory requirements. |
| Infrastructure integration | Connect to private databases, internal APIs, and existing data lakes without exposing them to the public internet. |
| Single sign-on (SSO) | Authenticate through your existing identity provider (Okta, Azure AD, etc.) for seamless team onboarding. |
| Network isolation | Deploy behind your own firewall, VPN, or AWS PrivateLink for end-to-end network control. |
| Multi-region deployment | Deploy Fused in multiple regions to achieve global availability and reduce latency. |
| Multi-tenant deployment | Deploy Fused to multiple teams within your organization. |
Requirements
Before provisioning, make sure the following are in place:
- Enterprise agreement — An active enterprise customer agreement with Fused. Contact the Fused team if you don't have one yet.
- Dedicated AWS account — An AWS account with IAM administrator access. We strongly recommend using an account dedicated to Fused so that permissions and billing stay isolated.
- Region selection — Choose the AWS region where your data already lives to minimize latency and cross-region transfer costs.
tip
Your Fused solutions engineer will walk you through the provisioning process and provide the exact requirements for your organization.
See also
- Connecting an Encrypted S3 Bucket — grant Fused access to SSE-KMS encrypted buckets
- Python installation — install the Fused SDK locally
- Secrets Management — store credentials securely
- Write UDFs securely — best practices for handling sensitive data