Where SmallStack Fits

This is SmallStack's home turf. Internal tools don't need flashy marketing pages — they need solid auth, a clean data-focused UI, audit trails, and reliable deployment. SmallStack delivers all of that with minimal setup. The admin-style layout with sidebar navigation is exactly what internal tool users expect.

SmallStack uses Django 6's built-in task framework with a database-backed worker — no Celery, no Redis, no message broker. Tasks are defined as decorated functions and run by a simple worker process. For most applications, this is all you need. It's already configured and the worker runs alongside your web process in production.

CRUD-heavy business apps are SmallStack's bread and butter. The admin-style sidebar layout, Django Admin for quick data management, and the activity tracking system make it natural to build internal business tools. Add your models, wire up views, and you have a working business application with audit trails and user management from the start.

SmallStack's core is server-rendered templates, but API support is on the roadmap. The Django ORM, auth system, background tasks, and deployment pipeline all work for API-first projects today — what's missing is the API layer itself. We're evaluating DRF and Django Ninja to find the right fit for SmallStack's philosophy of simplicity without sacrificing capability.

SmallStack's built-in help system already renders Markdown content from files with YAML front-matter, navigation, and search. For a simple docs site or blog, you're surprisingly close. For a full editorial CMS with rich content models, you'll want Wagtail — but SmallStack makes a good foundation to build on.

If your ML project needs a web UI for results, model management, or a dashboard alongside the API, SmallStack provides a solid base. The background task system can handle model inference jobs. But if you're building a pure prediction API with no web interface, a lighter framework is more appropriate.

SmallStack gives you auth, profiles, background tasks, and deployment — but SaaS products need billing, multi-tenancy, and flexible branding that SmallStack doesn't include today. You can build an MVP here, but you'll be adding a lot of plumbing yourself. SmallStack Pro 1.0 (releasing alongside SmallStack 2.0) will address several of these gaps with a flexible theme system, AI-assisted development, and managed hosting options.

E-commerce requires a deep stack of specialized features — product variants, inventory, cart sessions, payment processing, shipping, tax calculation — that SmallStack doesn't include. You'd be building all of that from scratch. Django-Oscar or Saleor are purpose-built for this and will save you months of work.

Django can absolutely scale to millions of users — Instagram proved that. But those systems require caching layers, load balancers, microservices, and database sharding that are far beyond SmallStack's scope. SmallStack is deliberately a single-server stack. It's designed to get you to production fast, not to handle Instagram-level traffic.