Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Doc FA cloud vs. self-hosting #2943

Open
synedra opened this issue Dec 10, 2024 · 0 comments
Open

Doc FA cloud vs. self-hosting #2943

synedra opened this issue Dec 10, 2024 · 0 comments
Assignees
Labels

Comments

@synedra
Copy link

synedra commented Dec 10, 2024

Here's an outline for a documentation page comparing self-hosting FusionAuth and using FusionAuth Cloud:
Introduction to FusionAuth Deployment Options
FusionAuth offers two primary deployment options: self-hosting and FusionAuth Cloud. This flexibility allows organizations to choose the best solution for their specific needs, security requirements, and infrastructure preferences.
Self-Hosting FusionAuth
Overview
Downloadable software that can be installed on your own infrastructure
Complete control over the deployment environment
Supports various deployment methods, including on-premises and cloud-based options
Key Features
Deployment Flexibility: Run FusionAuth in any environment, including production, UAT, staging, QA, and development
Data Residency Control: Host your own instance or choose an air-gapped deployment for enhanced security
Customization: Full control over the entire authentication system
Integration: Seamless integration with CI/CD pipelines and Kubernetes environments
Use Cases
Organizations with strict data residency requirements
Companies needing air-gapped deployments for maximum security
Enterprises with existing infrastructure and IT teams capable of managing self-hosted solutions
Businesses requiring complete control over their authentication environment
FusionAuth Cloud
Overview
Fully managed authentication service hosted by FusionAuth
Eliminates the need for infrastructure management
Provides a turnkey solution for authentication needs
Key Features
Scalability: Single-tenant architecture that allows for straightforward scaling without extensive planning[1]
Managed Updates: Automatic updates and maintenance handled by FusionAuth
SLA-Backed Reliability: 99.99% uptime SLA
Support: 24/7 engineer-led support
Use Cases
Startups and small to medium-sized businesses looking for a quick setup
Organizations without dedicated IT resources for managing authentication infrastructure
Companies prioritizing rapid deployment and minimal maintenance overhead
Businesses seeking predictable pricing and managed scalability
Choosing the Right Option
Factors to Consider
Security Requirements: Evaluate the need for air-gapped deployments or specific security controls
Compliance: Consider data residency and regulatory requirements
Resources: Assess available IT resources and expertise for managing self-hosted solutions
Scalability: Determine current and future scaling needs
Customization: Evaluate the level of customization required for your authentication system
Cost: Compare the total cost of ownership for self-hosting versus cloud-based solutions
Decision Matrix
Factor
Self-Hosting
FusionAuth Cloud
Control
High
Moderate
Maintenance
User-managed
Fully managed
Deployment Speed
Varies
Rapid
Customization
Extensive
Limited
Scalability
User-managed
Automatic
Cost Model
Infrastructure + License
Subscription-based

Conclusion
Both self-hosting and FusionAuth Cloud offer robust authentication solutions. The choice between them depends on your organization's specific needs, resources, and priorities. Evaluate each option carefully to determine which aligns best with your business requirements and long-term goals.

Output should be similiar to https://fusionauth.io/docs/get-started/core-concepts/hosted-login-vs-api-login

@synedra synedra added the Ritza label Dec 10, 2024
@synedra synedra self-assigned this Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant