Documentation

Deploy StopPaper with Docker. Docker Swarm by default, Kubernetes available for enterprises.

Quick start — Deploy in ~15 minutes

Already have a server and registry access? Here's the minimal path to get StopPaper running.

  1. Get registry credentials from us (contact to request access)
  2. Provision a server: 2 vCPUs, 4 GiB RAM, 80 GiB disk (e.g. DigitalOcean ~$29/mo)
  3. Install Docker 24+ with Compose v2 and enable Swarm
  4. Configure S3-compatible storage and env vars in the compose file
  5. Run docker swarm init then docker stack deploy -c docker-compose.yml stoppaper

Full details in the sections below.

What you'll need

Before deploying, make sure you have:

  • A server or VM meeting the minimum requirements
  • S3-compatible storage (AWS S3, DigitalOcean Spaces, MinIO, etc.) for file storage
  • Registry credentials from us (contact to request access)
  • A domain or IP for accessing the application

Deploy anywhere

StopPaper can be deployed in public cloud or private data centers—wherever your compliance needs require. Run it on AWS, GCP, Azure, DigitalOcean, or your own on-prem infrastructure. You control where your data lives.

Deployment options

StopPaper is delivered as container images. We deploy with Docker Compose and Docker Swarm by default. Organizations that prefer Kubernetes can access our images with registry keys.

Docker Compose + Swarm

Default deployment. Use our docker-compose stack with Docker Swarm for orchestration. Simple, battle-tested, and ready to run.

Kubernetes

For teams already on Kubernetes. Access our images from our registry with your company key. Manifests and Helm charts available.

Docker Compose with Docker Swarm

Our default deployment uses Docker Compose and Docker Swarm. Deploy the full StopPaper stack—API, workers, database, and services—with a single compose file. Swarm handles orchestration, scaling, and high availability.

# Initialize Swarm (if not already)
docker swarm init

# Deploy the stack
docker stack deploy -c docker-compose.yml stoppaper

Full docker-compose and stack configuration is provided when you get access. Includes MySQL, Redis, and all StopPaper services.

Tech stack

StopPaper is built on modern, proven technologies:

Backend

FastAPI, MySQL, Redis

Frontend

Next.js

Storage

S3-compatible object storage for files

Minimum requirements

StopPaper runs well on modest hardware. A single DigitalOcean droplet is a solid starting point—and scales easily later.

Recommended minimum (DigitalOcean)

2 vCPUs

Compute

4 GiB RAM

Memory

80 GiB

Disk

4 TB transfer

Bandwidth

~$29/month on DigitalOcean. Solid, reliable, and easy to scale when you need more.

Clients can scale to anything—bigger instances, multi-region S3 buckets, dedicated databases, and more. Start small, grow as you need.

OS & runtime

  • • Linux (Ubuntu 22.04 LTS or similar recommended)
  • • Docker 24+ with Compose v2
  • • For Swarm: Docker Swarm mode enabled

Kubernetes

For organizations running Kubernetes, we provide access to our container images. Pull from our private registry using credentials we issue to your company.

  • Container images for all StopPaper services
  • Kubernetes manifests and Helm charts (where applicable)
  • Deploy into your existing cluster or new one

Contact us to request Kubernetes access. We'll provision registry credentials and share deployment guides.

Image registry & access keys

StopPaper images are hosted in a private registry. Companies receive access keys to pull images for deployment—whether you use Docker Swarm or Kubernetes.

How it works

  • 1. Sign up or contact us for deployment access
  • 2. We issue registry credentials (username + token) to your company
  • 3. Use the credentials to pull images for Docker or Kubernetes
  • 4. Deploy with docker-compose/swarm or your preferred K8s setup

Keys are scoped per organization. Keep them secure and rotate as needed. Contact us at stoppaper1@gmail.com to request access.

Updates

Pull new images from our registry to upgrade. We release updates regularly. Your deployment config (env vars, volumes) stays the same—just update the image tags and redeploy.

Developer support

Need help with deployment, configuration, or troubleshooting? StopPaper was developed by ktechhub.

developer@ktechhub.com

Ready to deploy?

Get docker-compose files, Swarm configs, or Kubernetes access. We'll set you up with everything you need.

Contact us for access