This document describes the upcoming features and improvements planned for Stack Lifecycle Deployment.
- ✅ Migration from pip to uv (v3.7.0)
- ✅ Testing CLI with Python + Click
- ✅ Docker Compose support
- ✅ Kubernetes support (kind)
- ✅ REST API with FastAPI
- ✅ Web Dashboard
- ✅ Distributed Workers with Celery
- ✅ AWS, Azure, GCP support
- ✅ Remote State Management
- LDAP authentication
- Group and role synchronization
- Permission mapping from AD
- SSO with LDAP
- Multi-tenant configuration
Priority: High
Effort: 3 weeks
- Google OAuth
- GitHub OAuth
- Microsoft Azure AD
- GitLab OAuth
- Generic OAuth2 provider
- Social login in Dashboard
Priority: Medium
Effort: 2 weeks
- Data isolation per tenant
- Subscription management
- Plan limits (free, pro, enterprise)
- Billing and invoicing
- SaaS administration dashboard
- Metrics per tenant
Priority: Medium
Effort: 4 weeks
- Migrate to hexagonal/clean architecture
- Separate domain logic from infrastructure
- Implement Repository pattern
- Improve dependency injection
- Unit tests coverage >80%
- Automated integration tests
Priority: High
Effort: 6 weeks
- Implement enhanced caching with Redis
- DB query optimization
- Lazy loading of resources
- Background job optimization
- Async improvements
- Connection pooling
Priority: Medium
Effort: 3 weeks
- E2E tests with Playwright
- Performance testing with Locust
- Automated security scanning
- Code quality gates
- Mutation testing
Priority: Medium
Effort: 2 weeks
- Implement MCP server for SLD
- Expose SLD resources via MCP
- Tools for:
- Create and manage stacks
- Deploy/destroy infrastructure
- Query resource status
- Manage variables and secrets
- Integration with Claude Desktop
- Integration with other MCP clients
- MCP tools documentation
Priority: High
Effort: 4 weeks
Usage example:
{
"tools": [
{
"name": "sld_create_stack",
"description": "Create a new infrastructure stack",
"parameters": {...}
},
{
"name": "sld_deploy",
"description": "Deploy infrastructure changes",
"parameters": {...}
}
]
}-
AI Assistant for IaC
- Terraform code generation from natural language
- Review and improvement suggestions
- Security issue detection
- Suggested cost optimization
-
Chat Interface
- Chat in Dashboard for queries
- "Show me my stacks status"
- "How much am I spending on AWS?"
- "Create a new stack for a web app"
-
Predictive Analysis
- Future cost prediction
- Anomaly detection
- Optimization recommendations
-
LLM Providers
- OpenAI GPT-4
- Anthropic Claude
- Google Gemini
- Azure OpenAI
- Local models (Ollama)
Priority: High
Effort: 6 weeks
- Step-by-step guided flow
- Pre-configured templates:
- Web Application (3-tier)
- Microservices Architecture
- Data Pipeline
- ML Infrastructure
- Serverless API
- Real-time validation
- Preview of resources to create
- Cost estimation
- Integrated best practices
- Drag & Drop UI for architectures
Priority: High
Effort: 5 weeks
- Complete Dashboard redesign
- Dark mode
- Improved responsive design
- Interactive charts
- Real-time updates (WebSockets)
- Keyboard shortcuts
- Command palette (Cmd+K)
Priority: Medium
Effort: 4 weeks
- Official SLD chart
- Flexible configuration via values.yaml
- Sub-charts for components:
- API Backend
- Dashboard
- Workers
- Remote State
- Schedule
- Helm hooks for migrations
- CRDs for SLD resources
- Operators pattern
Priority: High
Effort: 3 weeks
Installation example:
helm repo add sld https://charts.sld.io
helm install my-sld sld/stack-lifecycle-deployment \
--set api.replicas=3 \
--set workers.autoscaling.enabled=true- Custom Resource Definitions:
- Stack
- Deploy
- Variable
- CloudAccount
- Reconciliation loops
- GitOps ready
- Integration with ArgoCD/Flux
Priority: Medium
Effort: 4 weeks
- SLD-specific runner
- Pre-built actions:
- sld-deploy
- sld-plan
- sld-destroy
- sld-validate
- Integration with GitHub Environments
- Approval workflows
- Secrets management
- Matrix builds for multi-cloud
Priority: High
Effort: 3 weeks
Usage example:
name: Deploy to Production
on:
push:
branches: [main]
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: sld/deploy-action@v1
with:
stack-name: prod-web-app
environment: production- Deployment on Google Cloud Run
- Auto-scaling of runners
- Pay-per-use model
- Integration with Cloud Build
- Secret Manager integration
Priority: Medium
Effort: 2 weeks
- Fargate runner tasks
- ECS Service for workers
- Integration with CodePipeline
- Secrets via Parameter Store
- IAM roles integration
Priority: Medium
Effort: 2 weeks
- Serverless runner on:
- AWS Lambda
- Google Cloud Functions
- Azure Functions
- Event-driven deployments
- Cost optimization
- Cold start mitigation
Priority: Low
Effort: 3 weeks
- Simultaneous deployment across multiple clouds
- Cross-cloud disaster recovery
- Cross-cloud cost optimization
- Unified billing dashboard
- Integration with Prometheus/Grafana
- Distributed tracing (Jaeger)
- Log aggregation (ELK/Loki)
- APM integration
- Custom metrics and alerting
- Policy as Code (OPA)
- Compliance checking (CIS, SOC2)
- Vulnerability scanning
- Automated secret rotation
- Enhanced audit logging
- Slack notifications
- Microsoft Teams
- PagerDuty
- Jira integration
- ServiceNow
- Datadog
- Git as source of truth
- Automatic drift detection
- PR-based workflows
- Automated rollback
- Template marketplace
- Community modules
- Verified providers
- Ratings and reviews
v3.8.0 (Auth)
- Onboarding time < 5 minutes
- 80% of users using SSO
- Zero security incidents
v4.0.0 (AI/MCP)
- 50% of deployments AI-assisted
- 30% reduction in configuration errors
- MCP adoption by community
v4.2.0 (Helm)
- 1000+ installations via Helm
- Deployment time < 5 minutes
- Community contributions
v4.3.0 (Runners)
- 10+ active runners
- 99.9% uptime
- Integration with top 3 CI/CD platforms
Want to contribute to the roadmap?
- Vote for features: Create an issue with label
feature-request - Propose new ideas: Open a discussion on GitHub
- Contribute code: Submit PRs for features in development
- Feedback: Share your experience and needs
Priorities are determined by:
- Community votes (30%)
- User impact (30%)
- Strategic alignment (20%)
- Effort vs value (20%)
2026 Q1 ████████░░░░░░░░ LDAP/OAuth/SaaS
2026 Q2 ░░░░░░░░████████░░ Refactoring
2026 Q3 ░░░░░░░░░░░░░░████ MCP + AI
2026 Q4 ░░░░░░░░░░░░░░░░░░ Wizard
2027 Q1 ████░░░░░░░░░░░░░░ Helm
2027 Q2 ░░░░████████░░░░░░ Runners
2027+ ░░░░░░░░░░░░██████ Future
- Issues: GitHub Issues
- Discussions: GitHub Discussions
- Email: [maintainer email]
This roadmap is a living document and will be updated based on:
- Community feedback
- Market needs
- Technological evolution
- Available resources
Last updated: October 2025
Next review: January 2026
Make infrastructure as code management accessible, secure, and efficient for all teams, with the power of AI and the simplicity of a click.
Have an idea that's not on the roadmap?
We'd love to hear it! Open an issue with the tag idea 💭