TaskCart's self-hosted SvelteKit architecture: A deep dive into custom Docker and dual payments

This review analyzes TaskCart's custom VPS infrastructure, including its Docker Compose architecture, dual-Redis setup, and complex dual-payment integration for indie founders considering self-hosting.

TL;DR

Best for: Indie founders seeking full control over their infrastructure, particularly those with complex multi-party billing requirements like direct freelancer payouts, and a willingness to manage their own ops. Skip if: You prioritize minimal infrastructure overhead, prefer managed services (PaaS), or have simple subscription billing needs that a single payment processor can handle. Bottom line: TaskCart demonstrates a robust, self-hosted approach for a complex SaaS, but it demands significant operational expertise and a clear understanding of trade-offs.

METHODOLOGY

This is a v0 review of TaskCart, drawing exclusively on the founder's published claims and technical details shared on Reddit. Our analysis covers the described tech stack, the custom Docker Compose infrastructure, and the dual-payment system as presented by the founder, lampropoulosss. We accessed the source signal on 2026-05-23. This review does not include independent performance benchmarks, long-term workflow assessments, or edge-case testing. Our update cadence for this tool will involve re-testing when founder claims diverge from observed behavior or when significant new architectural details emerge.

WHAT IT DOES

TaskCart is an all-in-one workspace designed for freelancers, aiming to consolidate tools like Trello, Stripe Billing, and Dropbox into a single platform. The founder, lampropoulosss, emphasizes a deliberate departure from Vercel/PaaS in favor of a self-hosted solution on a single Virtual Private Server (VPS).

Integrated Workspace Features

The platform offers features typical of a freelancer workspace, including Kanban boards for project management. The frontend is built with SvelteKit and Svelte 5, leveraging the new runes for reactive state management, particularly for drag-and-drop interfaces using svelte-dnd-action. Styling is handled by Tailwind CSS. The backend runs Node.js 20 with SvelteKit SSR endpoints, incorporating Better-Auth for role-based access control and OAuth.

Resilient Docker Infrastructure

TaskCart's core infrastructure relies on a custom Docker Compose setup on a VPS. The SvelteKit application is containerized using a multi-stage Alpine Linux Dockerfile, resulting in a small image size. This application runs with 4 replicas (deploy: replicas: 4) behind an Nginx reverse proxy, which handles load balancing. Deployments include an automated pre-flight migration step where an ephemeral db-push container executes drizzle-kit push to synchronize the PostgreSQL 16 database schema (managed with Drizzle ORM) before the main app replicas start.

Dual Redis and Cloud Backups

The system employs a dual-Redis setup. The first Redis instance acts as a primary for background jobs, managed by BullMQ. This handles tasks like PDF invoice generation and Nodemailer emails, using AOF persistence to prevent job loss on restarts. The second Redis instance is dedicated solely to caching, with a strict 512MB memory limit and an allkeys-lru eviction policy. For data durability, a custom pg-backup service routinely creates SQL dumps of the PostgreSQL database and securely pushes them to a remote Cloudflare R2 bucket, managing 7-day and 4-week retention policies automatically.

Complex Dual-Payment System

TaskCart's billing architecture addresses two distinct payment flows. For its own SaaS subscriptions, TaskCart uses Paddle as a Merchant of Record, integrating via webhooks and the Node SDK. Separately, to enable freelancers to bill their clients directly through the platform, TaskCart integrates Stripe Connect OAuth. This setup ensures that when a freelancer generates an invoice, the client pays via a Stripe hosted checkout link, and funds go directly to the freelancer's Stripe account. TaskCart explicitly states it never touches user funds in this process.

WHAT'S INTERESTING / WHAT'S NOT

What's interesting about TaskCart's architecture is the deliberate choice to self-host on a single VPS, moving away from common PaaS solutions like Vercel. This decision, while increasing operational complexity, grants the founders granular control over their environment and potentially reduces long-term infrastructure costs once optimized. The detailed Docker Compose setup, particularly the use of 4 replicas behind Nginx and the automated drizzle-kit push for schema migrations, indicates a thoughtful approach to deployment and resilience for a small team. The dual-Redis strategy—one for persistent job queues (BullMQ with AOF) and another for ephemeral caching (LRU eviction)—is a pragmatic design pattern for separating concerns and optimizing resource usage. The custom pg-backup service pushing to Cloudflare R2 is also a solid, cost-effective choice for data durability, avoiding vendor lock-in to a single cloud provider's backup solutions.

What's not as clear or is missing from the founder's pitch is the operational overhead associated with managing such a custom, self-hosted cluster. While the technical details are impressive, the effort required for monitoring, logging, security patching, and incident response for a small team (implied by the