> For the complete documentation index, see [llms.txt](https://docs.appfactor.io/52eJroWboQfTwsFl14gL/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appfactor.io/52eJroWboQfTwsFl14gL/provisioning-guide/dedicated-saas-instance.md). # Dedicated SaaS Instance ## Overview AppFactor Single-Tenant SaaS provides a single-tenant, isolated deployment of the AppFactor platform, delivered using a Single-Tenant SaaS model. Each customer receives a fully isolated AppFactor environment with dedicated compute, storage, and networking resources, while AppFactor manages the platform end-to-end. This model combines the operational simplicity of SaaS with the isolation, control, and compliance benefits typically associated with self-managed deployments. *** ## What is AppFactor Single-Tenant SaaS? AppFactor Single-Tenant SaaS is a managed, single-tenant AppFactor environment provisioned specifically for your organization. Unlike the shared AppFactor SaaS offering, no infrastructure or application components are shared with other customers. Each dedicated instance includes: * A private AppFactor control plane * Dedicated application workers * Isolated databases and storage * Dedicated networking and ingress All instances are fully managed, monitored, patched, and upgraded by AppFactor. *** ## Architecture This section describes the technical architecture of AppFactor Single-Tenant SaaS from a platform and operations perspective. #### Cloud Hosting By default, AppFactor Single-Tenant SaaS is hosted on Amazon Web Services (AWS). Each customer environment is deployed into a dedicated AWS account or isolated AWS environment managed by AppFactor. Other cloud providers may be supported by exception, subject to commercial agreement and technical feasibility. #### Platform Architecture * Single customer per environment * Dedicated AWS networking (VPC) * Isolated compute, storage, and data services * Managed control plane operated by AppFactor No infrastructure components are shared between customers. *** ## Deployment Model This section defines how single-tenant environments are provisioned, hosted, and operated. * **Provisioning**: New instances are provisioned on request following commercial agreement * **Hosting**: Cloud-hosted (region selection subject to availability) * **Isolation**: Single-tenant at the infrastructure and application layers * **Management**: Fully managed by AppFactor This is **not** a self-hosted or customer-managed deployment. *** ## Security and Isolation This section describes the technical isolation boundaries and security controls enforced by the platform. #### Tenant Isolation * Dedicated AWS VPC per customer * Isolated application runtimes * Dedicated data stores per environment * No cross-tenant network connectivity #### Security Controls AppFactor Single-Tenant SaaS applies security best practices aligned with managed AWS environments, including: * Network segmentation and security groups * Encryption in transit and at rest * Managed secrets and credentials * Continuous vulnerability management Security controls are applied consistently across all single-tenant environments. *** ## Compliance and Data Residency This section documents compliance-relevant capabilities for regulated environments. AppFactor Dedicated is designed for customers with stricter compliance or data residency requirements. Capabilities may include: * Region-specific deployments * Data residency guarantees * Support for regulated workloads Availability depends on cloud region and commercial agreement. *** ## Upgrades and Maintenance This section outlines lifecycle management responsibilities and change processes. AppFactor is responsible for: * Platform upgrades * Security patching * Availability and performance monitoring * Backup and disaster recovery Upgrades are coordinated to minimize customer impact and follow defined maintenance windows. *** ## Availability and SLAs This section describes availability targets and reliability commitments. #### Reliability and Resilience * Deployed on highly available AWS services * Redundant components across availability zones where applicable * Automated health checks and monitoring #### Backup and Recovery * Automated backups of critical data * Defined retention policies * Disaster recovery procedures managed by AppFactor Availability targets and recovery objectives are defined contractually. *** ## Configuration and Customization This section defines supported configuration surfaces and limitations. AppFactor Dedicated supports limited customization, such as: * Environment sizing * Region selection * Networking configuration * Integration endpoints Application-level customization beyond supported configuration options is not permitted. *** ## Support This section defines support scope and operational engagement. #### Managed Service Model AppFactor Single-Tenant SaaS is delivered as a fully managed service. AppFactor is responsible for: * Infrastructure operations * Platform monitoring and alerting * Incident response * Security patching and upgrades Customers are not required to perform operational maintenance. *** ## Subscriptions and Commercial Model This section provides a high-level overview of the commercial model. AppFactor Dedicated is offered as a **subscription-based service**. Pricing depends on: * Instance size * Region * Support tier * Contract term Contact AppFactor sales for pricing details. *** ## Testing & PoV - Sandbox Instances AppFactor provides sandbox environments that follow the same Single-Tenant SaaS architecture and operational model as production deployments, with lighter sizing and relaxed non-functional characteristics to support testing, evaluation, and proof-of-value (PoV) activities. Sandbox instances are fully isolated, managed by AppFactor, and hosted using the same core platform components, ensuring architectural consistency while allowing faster provisioning, reduced cost, and greater operational flexibility. While availability, performance, and retention guarantees may differ from production, sandbox environments accurately reflect real-world behavior for functional validation, integration testing, and customer evaluation. *** ## Frequently Asked Questions (FAQ) #### Is this a self-hosted deployment? No. AppFactor Single-Tenant SaaS is fully managed by AppFactor. Customers do not manage infrastructure, operating systems, or platform services. #### Do customers get access to the underlying infrastructure? No. Access is limited to supported application interfaces (UI, APIs, integrations). Infrastructure-level access is not provided. #### How is this different from shared SaaS? Single-Tenant SaaS provides dedicated infrastructure, isolated runtime components, and customer-specific data stores. Shared SaaS uses multi-tenant infrastructure. #### Can I choose the cloud provider and region? Region selection is supported where available. Cloud provider selection may be limited based on AppFactor support and commercial agreement. #### How are upgrades handled? Upgrades are performed by AppFactor during defined maintenance windows. Customers are notified in advance of planned changes. #### Can I customize the platform? Customization is limited to documented configuration options. Application code or platform modifications are not supported. #### Is data isolated from other customers? Yes. Each single-tenant environment has dedicated data stores and no cross-tenant access paths. #### What support level is included? Support levels depend on the subscribed plan and are defined contractually. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.appfactor.io/52eJroWboQfTwsFl14gL/provisioning-guide/dedicated-saas-instance.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.