How to Deploy a Web Application on a PaaS Platform

Writing an app is one job. Getting it live for real users is another. On a traditional server, deployment can mean setting up a machine, installing software and fixing errors for hours. On a PaaS platform, much of that work is already done, so you can go from code to a live link in a short time.

Quick answer: To deploy a web application on a PaaS platform, you create an environment for your language and framework, set resources and a database, upload or connect your code through Git or an archive, set your configuration values, and open the live URL to test. Then you add a custom domain and SSL, and set up monitoring and backups. Each step takes minutes on a managed platform.

New to PaaS? Start with our guide on what is PaaS and see the layers behind it in how PaaS works.

Before You Start: Get Your App Ready

A smooth deployment starts with a tidy project. Check these first:

• Your code is in version control. A Git repository makes updates easy to repeat.
• Your app runs locally. If it fails on your laptop, it will fail online.
• Secrets are not in your code. Passwords and keys belong in environment variables.
• Dependencies are listed. A file such as composer.json, package.json or requirements.txt tells the platform what to install.
• You know your database. Decide which engine you need, such as MySQL or PostgreSQL.

If you want to know which apps fit PaaS best, read our guide on what types of applications suit PaaS.

Step 1: Choose Your Stack

Pick the language and version your app needs. On our platform you choose this when you create an environment. Our application hosting page shows what we support, including PHP hosting and Laravel hosting, and our knowledge base covers other languages such as Node.js and Python.

Tip: Match the version you use locally. Version mismatches cause many first-day errors.

Step 2: Create an Environment

An environment is the home of your app. On our platform you open the dashboard, click New Environment and use the topology wizard. In the wizard you:

1. Choose the language tab for your stack
2. Pick the application server and version
3. Set resource limits, using flexible units called cloudlets, so your app can grow when it needs to
4. Choose the number of nodes
5. Turn on SSL if you want it from the start
6. Give the environment a name and click Create

Our knowledge base explains this in detail in its guide to creating an environment.

Step 3: Add a Database

Most apps need one. You can create a database in the same environment wizard or add it later. Our managed databases include MySQL hosting, PostgreSQL hosting, MariaDB hosting and MongoDB hosting.

Note the database host, name, user and password. You will add them to your app’s settings in a moment.

Step 4: Deploy Your Code

You usually have two ways to get your code onto the platform.

Option A: Git. Connect your repository, choose the branch and deploy. You can also turn on automatic updates so the platform checks the repository on a schedule and redeploys when there are new changes. Our knowledge base shows this in its guide to deploying a project through Git or SVN.

Option B: Archive upload. Pack your project as a zip or tar file, upload it through the deployment manager and choose the environment to deploy to. This is handy for a first test or for projects not yet in Git.

Git is better for teams and repeat releases. An archive is fine for a quick start.

Step 5: Set Your Configuration

Add your settings as environment variables instead of writing them into your code. Typical ones are:

• Database host, name, user and password
• App secret keys
• Mode settings such as production or debug off
• Third party API keys

Safety tip: Turn debug mode off in production, and never commit secrets to your repository.

Step 6: Run Setup Tasks

Many apps need one or more setup commands after the first deployment, such as installing dependencies, running database migrations or clearing caches. Do these through the platform’s terminal or deployment hooks if available. The exact commands depend on your framework.

Step 7: Open the App and Test

Open the app in your browser from the dashboard. Then check:

• The home page and key pages load
• Login and forms work
• Uploads work, and their size limits are enough
• The database saves and reads data
• Errors do not show sensitive details

If something fails, read the logs first. Most deployment problems are version, permission or configuration issues.

Step 8: Add Your Domain and SSL

A live link is good for testing. Real users need your own domain.

1. Point your domain to the environment as the platform instructs
2. Attach the domain in the dashboard
3. Turn on SSL so the site loads over HTTPS
4. Test again with the real domain

Step 9: Add Backups, Monitoring and Scaling Settings

Going live is not the end. Before real traffic arrives:

• Backups: confirm they run and test one restore
• Monitoring: check that you can see response time, errors and resource use
• Scaling: review resource limits so your app can handle a busy day
• Security: limit who can access the dashboard and use strong logins

Our PaaS security checklist and our guide on how to evaluate PaaS performance show what to check.

A Real-World Example

Think of a freelancer who has built a small booking app for a client. On their own server, it took two days to set up, secure and deploy the first version. On a managed platform, they create an environment, add a database, connect their Git repository, set the environment variables and deploy in under an hour. They spend the rest of the day testing and adding the client’s domain.

On the second release, they simply push new code. The platform pulls the change and redeploys. The freelancer spends their time improving the app instead of repairing servers.

Common Deployment Mistakes

• Choosing a different language version from the one used locally
• Leaving debug mode on in production
• Putting secrets inside the code
• Forgetting to run database migrations
• Skipping the staging test
• Not testing file uploads or size limits
• Never testing a backup restore

A Simple Deployment Checklist

Step	Done
Code in Git and runs locally	Yes or no
Stack and version chosen	Yes or no
Environment created	Yes or no
Database added	Yes or no
Code deployed	Yes or no
Variables set, debug off	Yes or no
Setup tasks run	Yes or no
App tested	Yes or no
Domain and SSL set	Yes or no
Backups and monitoring checked	Yes or no

Where to Go Next

If your app uses PHP, read our guide on how to deploy PHP applications on PaaS. For Laravel, see how to deploy a Laravel application on PaaS. If you use containers, read how to deploy Docker containers on PaaS. For production planning, see how to evaluate a PaaS platform for production.

 

Final Thoughts

Deploying on PaaS is mostly a repeatable routine: choose a stack, create an environment, add a database, deploy your code, set your configuration, test and go live. Once you have done it once, the next app is faster.

Ready to deploy your first app? Explore our PaaS platform, check our PaaS pricing or speak to our team.

 

Frequently Asked Questions

How long does it take to deploy an app on PaaS?
A simple app can be live within minutes to an hour once your code is ready. Larger apps take longer because of testing and configuration.

Do I need DevOps skills to deploy on PaaS?
Not deep ones. You need to know your app, your database and your settings. The platform handles servers and runtimes.

Should I use Git or an archive upload?
Use Git for teams and repeat releases. Use an archive for a quick first test.

Can I deploy more than one app?
Yes. You can create separate environments, for example one for staging and one for production.

What if my deployment fails?
Check the logs, confirm the language version, check your configuration and make sure dependencies installed correctly. Then ask support if you are still stuck.

Can I move my app to another provider later?
Usually yes, especially if you keep your code in Git and use standard stacks.