---
title: What is PaaS? | Shopware Community Hub
description: >-
Understand the fundamentals of Platform-as-a-Service (PaaS), its use cases,
and how it compares to other hosting models for Shopware projects.
canonical_url: 'https://hub.shopware.com/learn/unit/paas-what-is-paas'
---
# What is PaaS?
- Define Platform-as-a-Service (PaaS) and identify its key characteristics.
- Explore common use cases for PaaS in Shopware projects.
- Compare self-hosted, PaaS, and SaaS deployment models for Shopware.
# What is PaaS?
When planning to deploy and host a Shopware project, you'll have several options. Platform-as-a-Service (PaaS) has emerged as a powerful middle ground that balances control and convenience for many scenarios.
In this learning unit, you'll learn what PaaS is, why it matters for Shopware projects, and how it compares to other approaches.
## What Shopware PaaS means for Shopware Development
Shopware offers two PaaS solutions to accelerate Shopware development:
**Shopware PaaS (Upsun-based, formerly Platform.sh-based)** provides a production-ready environment in minutes, built on Upsun infrastructure. You can focus on building features and customizations while the platform handles server configuration, database setup, and deployment processes.
**Shopware PaaS Native** is Shopware's next-generation cloud-native platform, offering enhanced performance, simplified management, and deeper integration with Shopware ecosystem tools.
This learning path focuses primarily on **Shopware PaaS (Upsun-based)** concepts and workflows. While the fundamental PaaS principles apply to both solutions, specific configuration details and CLI commands may differ between the two platforms. Always refer to the current documentation for your chosen platform.
**Real scenario:** A client of your Shopware agency needs a new Shopware shop. Without Shopware PaaS, you'd spend time setting up:
- Web servers with proper PHP configuration.
- MySQL/MariaDB with optimal settings for Shopware.
- Redis for caching and sessions.
- Elasticsearch for product search.
- SSL certificates and CDN setup.
- Backup and monitoring systems.
- Staging and development environments.
**With Shopware PaaS:** You clone a repository, push your code, and everything is deployed automatically with all services configured and optimized for Shopware.
**The bottom line:** Shopware PaaS lets you focus on building features and customizations instead of managing infrastructure.
PaaS sits between Infrastructure-as-a-Service (IaaS), which provides bare virtual machines, and Software-as-a-Service (SaaS), which offers ready-to-use applications. PaaS gives you a pre-configured platform on which to deploy your own application code.
## Key Characteristics of PaaS
Shopware PaaS offers:
1. **Infrastructure abstraction**: The provider manages hardware, OS, and core services.
2. **Developer-friendly tooling**: CLI tools, dashboards, APIs for deployments.
3. **Built-in scalability**: Easily scale resources up or down based on demand.
4. **Automated processes**: Handling of backups, updates, and security patches.
5. **Integrated services**: Pre-configured databases, caching, search engines, and other services.
6. **Standardized environments**: Consistent development, staging, and production environments.
To see Shopware PaaS in action, check out the [Case Studies](https://www.shopware.com/en/shopware-paas/).
## PaaS Use Cases for Shopware
PaaS proves particularly valuable for Shopware projects in the following scenarios:
### Use Case One: Agency Partners Managing Multiple Projects
For agencies handling multiple client projects, PaaS offers:
- Standardized deployment processes across all clients.
- Less time spent on infrastructure.
- Consistent environments for development, testing, and production.
- Easier project handovers.
### Use Case Two: Projects with Variable Traffic Patterns
Ecommerce sites often experience traffic spikes during sales events or seasonal peaks. PaaS provides:
- Easy scaling to handle traffic surges.
- Efficient resource utilization during quiet periods.
- Automatic scaling based on predefined rules.
- Pay-for-what-you-use cost models.
### Use Case Three: DevOps-Oriented Teams
Teams practicing modern development approaches benefit from our predefined, optimized workflows that can be optionally adapted:
- Integrated deployment workflows.
- Infrastructure-as-code capabilities.
- Simplified dev-ops collaboration between.
- Feature branch environments for testing changes in isolation.
## Comparing Deployment Models
Let's examine how PaaS compares to other common deployment options for Shopware projects:
| Aspect | Self-Hosted | PaaS | SaaS |
|--------|-------------|------|------|
| **Infrastructure Management** | Full responsibility | Managed by provider | Fully managed |
| **Deployment Control** | Complete control | Control over application | Limited or no control |
| **Customization** | Unlimited | High | Limited |
| **Operational Effort** | High | Medium | Low |
| **Scaling Complexity** | Complex | Simplified | Automatic |
| **Cost Predictability** | Predictable | Variable | Fixed |
| **Resource Optimization** | Manual | Semi-automated | Fully automated |
| **Security Responsibilities** | Full stack | Shared | Mostly provider |
### Self-Hosted vs. PaaS
- **Self-hosted:** Teams manage servers, scaling, security, backups, and configs.
- **PaaS:** Team focuses on the Shopware application itself, while the platform handles infrastructure, scaling, backup and updates.
### PaaS vs. SaaS
- **PaaS:** Full control over Shopware application code, custom extensions, manual updates, flexible integrations.
- **SaaS (Software as a Service like Shopware Cloud):** Pre-deployed, auto-updated, limited customizations and integration options.
## Choosing the right Model for your Project
When selecting between self-hosted, PaaS, or SaaS for Shopware, consider:
1. **Technical expertise**: Does your team have the skills to manage infrastructure?
2. **Budget constraints**: How do upfront costs compare to ongoing operational costs?
3. **Customization needs**: How much do you need to customize the Shopware core?
4. **Scaling requirements**: What are your expectations for traffic growth?
5. **Compliance requirements**: Do you have specific data residency or security needs?
6. **Time to market**: How quickly do you need to launch and iterate?
PaaS offers an optimal balance of control and efficiency.
Ready to get hands-on? The official documentation provides a comprehensive [step-by-step guide](https://developer.shopware.com/docs/products/paas/shopware-paas/build-deploy.html#first-deployment) covering CLI setup, repository configuration, and deployment processes.
## Key Takeaways
- **Shared Responsibility**: PaaS = infrastructure by provider, Shopware by you.
- **Clear Handovers**: Documentation avoids issues.
- **Lifecycle Understanding**: All stakeholders should understand the full project lifecycle.
- **Proactive Communication**: Regular updates between stakeholders help identify and resolve issues early.
## Next Steps
In the next unit, we'll explore the project lifecycle for PaaS-based Shopware deployments and understand each stakeholder's responsibilities.