Show HN: Specific (YC F25) – Build backends with specifications instead of code (specific.dev)
Specific is a platform for building backend APIs and services entirely through natural-language specifications and tests, without writing code. We then automatically turn your specs into a working system and deploy it for you, along with any infrastructure needed.
We know a lot of developers who have already adopted spec-driven development to focus on high-level design and let coding agents take care of implementation. We are attempting to take this even further by making the specs themselves the source of truth. Of course, we can’t blindly trust coding agents to follow the spec, so we also support adding tests that will run to ensure the system behaves as expected and to avoid regressions.
There is so much ground to cover, so we are focusing on a smaller set of initial features that in our experience should cover a large portion of backends:
- An HTTP server for each project. Authentication can be added by simply stating in the spec how you want to protect your endpoint.
- A database automatically spun up and schema configured if the spec indicates persistence is needed.
- External APIs can be called. You can even link out to API docs in your specs.
You currently can’t see the generated code, but we are working on enabling it. Of course, we don’t claim any ownership of the generated code and will gladly let you export it and continue building elsewhere.
Specific is free to try and we are really eager to hear your feedback on it!
Try it here: https://app.specific.dev
6 comments
[ 1.9 ms ] story [ 23.4 ms ] threadIf Specific regenerates code from the spec each time (which I'm not sure it does), there's the potential for different code each time even for parts of the spec that haven't changed. This seems like a nightmare for maintainability and debugability.
What will the pricing be after the beta? And what are you exactly offering? Only a database or also authentication or storage?
Can you maybe compare it to something established like Supabase?
There are definitely cases where the spec is much easier to understand than the code that implements it.
Think systems with complex lifecycles or lots of required boilerplate.
Have you thought of embedding the specs into existing code?
E.g.
Passing tests is a measure for the fitness of the system; how it achieves this goal doesn't matter. The code itself might be awful, or only work due to side effects or emergent properties, but it works!