The Problem
Teams using Django + Celery need to monitor Celery tasks, but:
- Flower: Requires a separate process (port 5555)
- Extra Infrastructure: Additional container, process management
- Context Switching: Jumping between Django Admin and Flower
“Celery observability inside Django admin (no Flower, no extra process)” — HackerNews Show HN (2026.01.21)
Developers want to manage everything within the familiar Django Admin interface.
Market Analysis
| Aspect | Details |
|---|---|
| Target Market | Django + Celery teams |
| TAM | Django ecosystem $500M+ |
| Competition Status | BLUE (niche market) |
Competitive Landscape
| Solution | Pricing | Weakness |
|---|---|---|
| Flower | Free | Requires separate process |
| django-celery-monitor | Free | Limited features, unmaintained |
| Prometheus + Grafana | Free | Complex setup, overkill |
Differentiation: Native Django Admin integration, zero extra processes
Solution
Core Features
Django Admin Integration
# settings.py INSTALLED_APPS = [ ... 'celery_admin_observability', ]Real-time Dashboard
- Worker status (online/offline)
- Queue length and throughput
- Failed task list
Task Management
- Task retry
- Task revocation
- Result inspection
Alerts
- Slack/Email on task failure
- Queue backlog warnings
MVP Development
| Aspect | Details |
|---|---|
| Timeline | 3 weeks |
| Complexity | Low |
| Tech Stack | Python, Django, Celery Inspect API |
MVP Scope
- Worker status display
- Recent task list
- Failed task retry
Revenue Model
| Tier | Price | Features |
|---|---|---|
| Open Source | Free | Basic features |
| Pro | $29/mo | Alerts, advanced dashboard, priority support |
| Enterprise | $99/mo | SSO, audit logs, SLA |
Projected MRR: $1K-5K (after 12 months)
Note: Open-source base may make monetization challenging. Strong Pro feature differentiation required.
Risks
| Risk | Level | Mitigation |
|---|---|---|
| Technical | L | Leverage Celery Inspect API |
| Market | M | Niche market, limited TAM |
| Execution | L | Simple MVP |
Why This Idea
Django + Celery is an extremely common combination in Python web development. Flower is the standard but the “separate process” friction exists. Native Django Admin integration significantly improves developer experience. However, limited market size and open-source competition require a careful monetization strategy.
Are you a Django + Celery user? Share your thoughts in the comments!