Skip to content

Deploy Flask App on Seenode | Flask Hosting & Deployment Guide

This guide will walk you through deploying your existing Flask application on seenode. We’ll use Gunicorn as our production WSGI server.

Before you begin, ensure you have:

  • A seenode account at cloud.seenode.com
  • Git configured on your machine
  • Existing Flask project ready to deploy

Ensure your project is configured for production. Your project should have an app.py file and a requirements.txt. seenode will look for an app instance in your app.py file.

app.py
from flask import Flask
app = Flask(__name__)
@app.route("/")
def hello_world():
return "Hello, from Seenode!"

Your requirements.txt should include flask. For production, we also recommend a WSGI server like gunicorn:

requirements.txt
flask
gunicorn
  1. Push to Git

    Commit your project and push it to GitHub or GitLab.

  2. Create a Web Service

    From the seenode Dashboard, create a New Web Service, connect your Git provider, and select your Flask project’s repository.

  3. Configure Build & Start

    Configure your service’s settings. For a typical Flask app, you can use the following:

    • Build Command:
      pip install -r requirements.txt
    • Start Command:
      gunicorn app:app --bind 0.0.0.0:${PORT:-80}
    Configure Build & Start: Port field
  4. Choose Pricing Tier

    Select your preferred instance size and create the service.

  5. Deploy

    Click Create Web Service and watch logs until your web service is live.

  6. Success

    Once complete, your application will be accessible via your service’s URL.

If you don’t have a Flask project yet:

Option 1: Use our Template (Recommended)

Option 2: Create from Flask Docs + seenode Setup

Follow the official Flask documentation to create a new project, then return here for seenode-specific deployment steps.

seenode-Specific Setup Steps:

  1. Create app.py with Flask app
  2. Add requirements.txt with Flask and Gunicorn
  3. No additional configuration needed

Now that your Flask app is deployed, here are some recommended next steps: