Where z4j is going.

Shipped features are locked. Future work is signaled by community usage, not our imagination. And we'll tell you what we won't build, too.

v1.0.0 (now)

released

• 6 engine adapters + 6 scheduler adapters
• Unified action surface
• Reconciliation worker
• RBAC UI polish + /settings/memberships
• Multi-user invitations + SMTP auto-send
• Password reset flow
• HMAC-chained audit log
• Rate limits on all unauthenticated endpoints
• Gmail + Mailgun + Brevo SMTP presets

v1.1 (next)

next

• z4j-saq adapter (Simple Async Queue)
• z4j-procrastinate adapter (Postgres-backed)
• Schedule create/update UI (currently read-only for rq-scheduler, APScheduler)
• Gmail OAuth2 integration (currently SMTP app-password only)
• Agent version mismatch banner
• Audit log CSV export
• Grafana dashboard template for /metrics
• Helm chart

v1.x (community-driven)

planned

• PagerDuty integration
• Alert suppression / snooze windows
• Escalation policies
• Root-task aggregation (one notification per chord/group failure)
• TimescaleDB evaluation for trends
• Horizontal agent scaling
• SLA monitoring (task-duration percentiles + tag thresholds)

v3 (multi-language)

intent

• z4j-go-asynq: first non-Python agent
• z4j-java-quartz: Spring @Async / @Scheduled coverage
• z4j-rust-apalis (conditional)
• Wire protocol + schema already language-agnostic

Never planned

no

• JavaScript queues (BullMQ, Bee): BullBoard / Arena cover these
• Ruby / Sidekiq: mature first-party tooling exists
• PHP / Laravel Horizon: first-class in Laravel already

Shape the roadmap

GitHub Discussions is where we talk about what to build next. We read everything.

Discussions Open an issue