# Deployment Models Looply offers a range of flexible deployment models designed to meet the unique needs of enterprises across different industries, regulatory environments, and technical landscapes. All models are built on the same cloud-native, serverless core — allowing for infinite scalability, low operational overhead, and strong security by design. This guide outlines each deployment model in detail, including technical ownership, use cases, and operational benefits. *** ### 1. Looply Public Cloud - Multi-Tenant SaaS Overview This is the default and most common Looply deployment. Your organization is provisioned as a logically isolated tenant within our managed multi-tenant environment, hosted on AWS in the EU (Ireland) region. Looply handles everything: provisioning, updates, scaling, backups, and security. All infrastructure is fully managed. #### Ideal For * Organizations that prefer a plug-and-play SaaS solution * Enterprises with no internal DevOps or AWS teams * Customers who need fast time-to-value #### Benefits * No infrastructure setup or maintenance * Rapid onboarding — be live in hours * Secure, enterprise-grade hosting with automatic scaling * Patching and upgrades managed entirely by Looply * Full role-based access control and audit logs included #### Customer Responsibilities * Sign up for Looply and invite team members * Connect Microsoft Entra ID (Azure AD) tenant * Install SAP ABAP add-on and expose required endpoints *** ### 2. Looply Private Cloud - Looply Managed #### Overview This model offers a balance between complete isolation and a managed service. Looply creates and manages a dedicated AWS sub-account on your behalf. The environment is exclusively yours but operated and monitored by Looply. This gives you many of the benefits of private cloud with none of the infrastructure maintenance burden. #### Ideal For * Enterprises who want tenant isolation without taking on DevOps responsibilities * Regulated organizations requiring dedicated resource control * Customers scaling across business units or geographies #### Benefits * Dedicated AWS account, isolated from all other tenants * Managed by Looply, including updates, observability, and maintenance * Custom AWS region or security configuration available on request * No infrastructure management required by customer #### Customer Responsibilities * Customers are required to complete all responsibilities listed under the Multi-Tenant SaaS model. * Approve account provisioning and region selection * Coordinate access for any enterprise-specific tools (optional) *** ### 3. Customer-Owned Private Cloud - Looply Managed #### Overview Looply can be deployed directly into your AWS account. In this model, Looply provides you with infrastructure templates and deployment tooling to provision and manage the environment within your own cloud footprint. You maintain full visibility and control over the infrastructure while still leveraging Looply's cloud-native capabilities. #### Ideal For * Enterprises with strict internal policies requiring all systems to be hosted in their own AWS accounts * Teams with DevOps maturity and AWS management capabilities * Customers with custom networking, logging, or compliance tooling #### Benefits * Full infrastructure control (IAM, VPC, logging, observability) * Deploy Looply alongside other internal workloads or data lakes * Integrate with your enterprise monitoring and incident response stack * Optional customization of VPC and subnet structure #### Customer Responsibilities * Customers are required to complete all responsibilities listed under the Multi-Tenant SaaS model. * Maintain the underlying AWS environment (costs, IAM, upgrades) #### Looply Responsibilities * Deploy using Looply-provided CloudFormation or Terraform templates * Provide infrastructure-as-code templates and versioning * Push platform updates, security patches, and major features * Provide integration support during provisioning and go-live *** ### Shared Benefits Across All Models Regardless of the deployment model, all Looply instances come with: * Auto-scaling, serverless architecture * Microsoft 365 and SAP integration capabilities * Secure token-based authentication * Real-time notifications, adaptive card support, and visual workflow builder * Developer-friendly, no-code/low-code interface * Monitoring, error handling, and audit logging by default *** ### Choosing the Right Deployment Model Here’s a quick guide to help you select the best fit: {% hint style="info" %} Scroll horizontally to compare all deployment models listed the table below {% endhint %}
FeaturesLooply Public Cloud (Multi-Tenant, Looply-Managed)Looply Private Cloud (Dedicated Tenant, Looply-Managed)Looply Private Cloud (Customer-Managed)
Who Manages Infrastructure?LooplyLooplyCustomer
Who Owns AWS Account?Shared (Looply’s AWS environment)Dedicated AWS account per customer (Managed by Looply)Customer-provided AWS account
Best ForBusinesses seeking cost-effective, fully managed SaaS with strong securityEnterprises needing compliance, data isolation & fully managed infrastructureHighly regulated enterprises needing full control over infra
Data IsolationLogical isolation via IAM, DynamoDB partitioning, and API securityFull physical isolation(dedicated AWS resources)Full physical isolation (customer controls AWS setup)
Data Residency ControlLimited region support predefined by Looply (customer can choose from available regions)Customer can choose any AWS regionCustomer can choose any AWS region
Compliance ReadinessSecure by design built on SOC2/ ISO 27001 compliant AWS infrastructureSOC 2 / ISO 27001 compliance-ready, with dedicated infrastructureCustomer responsible for compliance certification
Network SecurityMulti-tenant architecture with IAM-based access controls, API Gateway protection, and AWS WAF. All traffic is encrypted in transit.Dedicated VPC per customer, PrivateLink for internal AWS service access, tenant-specific IAM roles, and encrypted communications.Dedicated VPC per customer, PrivateLink for internal AWS service access, customer-controlled network security policies, and encrypted communications.
Outbound API AccessShared NAT Gateway with static IP for whitelistingDedicated NAT Gateway per customer with static IP, with optional PrivateLink-based outbound API access for enhanced securityDedicated NAT Gateway per customer with static IP. Customers can choose to restrict outbound internet access entirely using VPC PrivateLink, ensuring private-only API connectivity
Security ModelIAM-based tenant isolation, API authentication, encryption (at rest & in transit), AWS GuardDuty monitoringVPC isolation, PrivateLink, IAM-based role filtering, API authentication, encryption (at rest & in transit), AWS GuardDuty monitoring, tenant-specific IAM roles, dedicated security policies based on customer requirementsIdentical to Private Cloud (Looply-Managed)
Provisioning & Access ControlFully managed by LooplyLooply provisions and manages all infrastructure, including ongoing optimizations and updatesLooply provisions infrastructure in customer’s AWS account using securely shared credentials (e.g., temporary IAM roles, access vault). Infrastructure-as-Code (IAC) deployment requires client secrets (Serverless Framework). Customer is responsible for access governance after provisioning.
Software UpdatesAutomatic (Looply maintains version control & security patches)Automatic (Looply ensures all instances remain at the latest service pack level)Customer-defined(Looply provides updates, but customer led rollout)
Firefighter Access & Update ControlFull control (Looply manages everything, no customer intervention required)Looply has full admin access for patches, updates, and troubleshootingLooply requires ad-hoc 'Firefighter Access' for applying patches, upgrades, and troubleshooting. Access is temporary, controlled via IAM, and revoked after completion.
Support & Troubleshooting ModelFull support (Looply manages infrastructure, instant issue resolution with 24/7 monitoring )Full support (Looply has direct access to logs, monitoring, and security patches. Response time SLAs are flexible and defined contractually based on business needs)Customer IT team is primary support, Looply offers ‘Advisory Support’ with a troubleshooting SLA defined contractually, dependent on customer-provided access
Migration FlexibilityCan migrate to Private Cloud later(data export/import process)Easier transition between Looply-Managed and Customer-Managed modelsCustomer fully responsible for migrating out
Customization & IntegrationsStandard setup, limited customizationSome customization (branding, integrations, policies)Full control over integrations & network security
Disaster Recovery & High AvailabilityServerless architecture with automated scaling, multi-AZ support, and Looply-managed backupsServerless architecture with automated scaling, multi-AZ support, and Looply provides automated backups by default, with customizable retention policies based on customer requirementsServerless architecture with automated scaling, multi-AZ support, but customer responsible for backup policies
Performance & ScalingAuto-scaling based on AWS Lambda & DynamoDB on-demand scalingLooply-optimized scaling with dedicated tenant resourcesAuto-scaling enabled, but customer governs configuration
Data Retention & Backup PoliciesFully Configurable retention & standard Looply defined backup policiesFully Configurable retention & customizable backup policiesFully Configurable retention & customizable backup policies
Infrastructure CostIncluded in Looply’s pricing (No additional AWS cost to customer)Included in Looply’s pricing (No additional AWS cost to customer)Customer pays directly for AWS infrastructure usage
Usage + Licensing CostMetered based on usage + flat subscription fee (includes hosting, management, and support)Metered based on usage + Flat subscription fee (Looply manages software & updates)Flat subscription fee (Looply provides software updates, but customer manages infrastructure)
### Not Sure Which Model Is Right For You? Reach out to our team at or schedule a deployment planning call. We’ll help you align hosting with your security, compliance, and operational goals. > Architecture diagrams and data flow overviews available upon request.