Hey — Ray here, a founder working in an adjacent devtools space. Genuine peer question, not a pitch.
I was reading through ScaledSearch. The migrate part feels intentionally concrete already: migrate import creates a V000__baseline.yaml, apply --dry-run works offline, rollback is explicit in the YAML, and the alias-swap example handles zero-downtime index changes in a practical way.
The thing that made me pause is the roadmap table: audit, bench, monitor, tune, and cost are all marked “Coming soon.” Those feel like separate areas of production scar tissue, not just extra CLI commands.
My question: are you planning to build the next tools mostly from your own Elasticsearch/OpenSearch experience, or are you already trying to bring in outside search engineers for specific slices like audit or bench?
Short reply is plenty. I’m asking because I’m trying to understand where early devtool maintainers hit the line between “I can ship this myself” and “this needs the right contributor with lived production context.”
Hey — Ray here, a founder working in an adjacent devtools space. Genuine peer question, not a pitch.
I was reading through ScaledSearch. The
migratepart feels intentionally concrete already:migrate importcreates aV000__baseline.yaml,apply --dry-runworks offline, rollback is explicit in the YAML, and the alias-swap example handles zero-downtime index changes in a practical way.The thing that made me pause is the roadmap table:
audit,bench,monitor,tune, andcostare all marked “Coming soon.” Those feel like separate areas of production scar tissue, not just extra CLI commands.My question: are you planning to build the next tools mostly from your own Elasticsearch/OpenSearch experience, or are you already trying to bring in outside search engineers for specific slices like
auditorbench?Short reply is plenty. I’m asking because I’m trying to understand where early devtool maintainers hit the line between “I can ship this myself” and “this needs the right contributor with lived production context.”