Request: Split Switchyard into Separate Railway Templates for Convenience
First off, thank you for building Switchyard — it’s a great all-in-one solution for feature flags, autoscaling, job scheduling, and observability.
Right now, deploying Switchyard means setting up the entire stack in one Railway template, even if a project only needs one or two of its features. This can lead to unnecessary services, increased costs, and extra complexity for smaller deployments.
Proposal
Split Switchyard into separate, independent Railway templates for the following core functionalities:
- Feature Flags – Contextual rules, percentage rollouts, etc.
- Autoscaling – General service autoscaling without job scheduling.
- Worker Scheduling – Queue handling + autoscaling worker pool.
- Incident Reporting – Log/metric-based incident detection and webhook forwarding.
- Observability – Prometheus + Grafana dashboard for internal metrics.
Benefits
- Deploy only the parts needed for a project
- Lower resource usage and simpler deployments
- Easier onboarding for users who want to try a single feature first
- Clearer upgrade paths for each module without affecting unrelated components
Possible Approach
- Keep the current all-in-one template for full deployments
- Create separate Railway templates for each module
- Document how modules can integrate if needed
Example use case:
A team may only need Worker Scheduling to offload tasks to autoscaling workers without setting up feature flags, incident reporting, or observability. Having it as a standalone Railway template would greatly simplify their setup and reduce service overhead.
Would love to hear your thoughts on whether this modular approach fits with the project’s roadmap.
Request: Split Switchyard into Separate Railway Templates for Convenience
First off, thank you for building Switchyard — it’s a great all-in-one solution for feature flags, autoscaling, job scheduling, and observability.
Right now, deploying Switchyard means setting up the entire stack in one Railway template, even if a project only needs one or two of its features. This can lead to unnecessary services, increased costs, and extra complexity for smaller deployments.
Proposal
Split Switchyard into separate, independent Railway templates for the following core functionalities:
Benefits
Possible Approach
Example use case:
A team may only need Worker Scheduling to offload tasks to autoscaling workers without setting up feature flags, incident reporting, or observability. Having it as a standalone Railway template would greatly simplify their setup and reduce service overhead.
Would love to hear your thoughts on whether this modular approach fits with the project’s roadmap.