We built Dropstone because we were tired of starting from zero every time we opened an AI coding tool.
Dropstone learns, remembers, and evolves with your projects building a persistent understanding of your codebase, architecture, and workflow. It s designed to grow with you, not reset after every session.
We ve just launched it on Product Hunt and would love your thoughts on how memory should shape the next generation of developer tools. Your feedback will help us refine what s coming next.
Dropstone
Dropstone 1.5 is the first release from our new monthly cycle. Every month my team at Blankline tests the strongest open AI coding models, rebuilds the runtime around whichever wins, and ships.
This cycle we focused on two things. Cost, and safety.
On cost. Dropstone Pro and Heavy 1.5 run on trillion-parameter class open-weight models, the same scale that closed labs like Anthropic charge a premium for. We spent the month measuring what each coding session actually costs us, then squeezing it. $15 a month gets you about 450 deep coding sessions a week. Claude Code Pro gives you 150 to 225 for $20. On capability, Dropstone Pro 1.5 trades blows with Claude Opus 4.7. We match or beat it on most other coding work at a fraction of the price.
On safety. We built Dropstone safe enough to use on our own internal codebase first. Every file write, every shell command, every network call asks before it runs. Everything runs on US servers. Nothing is stored anywhere. That same safety boundary ships to every tier, Free, Pro, and Heavy. Using DeepSeek or Kimi through Dropstone is meaningfully safer than reaching for them directly.
Full math, benchmarks, and the honest losses are in our report: https://blankline.org/research/d...
@santosharron Congrats on the launch Santosh. the monthly model re-baseline idea is interesting but I'd want to understand how you manage coding behaviours cross model, they can be very different and for refactors etc, might be a risk?
The monthly re baseline idea makes sense. Coding models changes so fast that the best option can shift quickly. How do you decide when a new model is stable enough to become the default for Dropstone?
Dropstone
@ada_johnsen Our eval team runs a fixed harness monthly across capability, cost-of-service, and safety-of-integration, and whichever model wins the composite score for that tier becomes the default.
The monthly rebaseline is the part I’d want to understand before switching. If Heavy moves off Kimi in 1.6, can I pin a repo to the 1.5 behavior for a while, or does the CLI always follow the current winner?
Dropstone
@novamaker01 Yes, you can always switch back and use Heavy 1.5. When Eval Team performs a monthly rebaseline and updates the baseline model it doesn't remove your ability to access older supported versions and you are not forced to follow the current version if you prefer to stick with what you know works for your codebase.
Polyvia
2x Claude Code's usage at $15/mo: Auto-benchmarking open-weight models monthly and rebuilding around the best one is a bold operating model. How do you keep the agent's behavior/context consistent for users when the underlying model swaps each month? Continuity across model changes seems like the tricky part.
Mailwarm
Can teams bench host if they need stricter compliance?
DiffSense
But kimi is like 2% of Claude costs right? For devs that need masive amounts of coding power. monthly subscriptions isnt the solution. All you can eat at 2% is what we need!!! 🙏 😬