We are not ready to sell Boottify yet. We are ready to be tested, and we would rather be tested by you than discover the gaps after someone has paid.
If you build software — as a team or on your own — we are looking for a small number of people to run something real on the platform, free, while we are still in this phase.
What you would actually be trying
Boottify deploys and hosts your application. You point it at a repository, pick a plan, and it provisions a Kubernetes namespace, a database, a subdomain or your own domain, and TLS. From there you get logs, metrics, environment variables, backups, scaling, and the usual start / stop / restore controls.
ForgeHub is the part that faces your clients. Each project moves through defined stages — discovery, design, content, testing, deployment — and your client sees the stages you choose to show them, approves work in the ones that need approval, raises change requests, and signs off testing. Taking part earns them a real discount on the final invoice, which is the bit we find most interesting and the bit that has been exercised least.
Every instance is yours. Your ForgeHub connects to your own GitHub, your own S3 bucket, your own email sender — we do not put our credentials in your application, and there is now a check that refuses to write your environment if one of ours ever ended up there.
Why we are asking rather than launching
We have spent the last weeks finding our own bugs, and we have written openly about the uncomfortable ones: a confirmation dialog that rendered nothing, so every destructive button silently did nothing. A pricing page advertising dollars while we charged euros. An endpoint that authenticated you correctly and then streamed another customer’s deployment logs.
We found those. That is the problem. Almost nothing on this platform has been driven end to end by somebody who is not us, and we know exactly what that means: the next class of bug is the one our own assumptions cannot see. We will be running a full project and deployment ourselves in parallel — but our test will have our blind spots in it.
We would rather fix that with a handful of patient people now than hand a paying client something that almost works.
What we are asking for, and what you get
We are looking for a solo developer or a small team willing to deploy something real — a side project, an internal tool, a client site you are comfortable running alongside your existing setup — and tell us plainly where it breaks.
You get the platform free through this phase, a direct line to the people building it rather than a ticket queue, and your feedback shaping decisions while they are still cheap to change. If you run client projects, you get to try the contribution model and tell us whether it is something your clients would actually use.
We will tell you what is still rough before you start, not after. There is a short, honest list and we will send it to you.
What it costs you
Time, and some tolerance. Things will break. When they do we want to hear about it in detail, and we will fix them quickly — that is the entire point of this phase.
We are not asking for a testimonial, a case study, or a commitment to stay. If you try it and it is not for you, tell us why and we will have got what we needed.
Get in touch
Email hello@boottify.com with a sentence about what you would deploy. That is enough — no form, no demo call unless you want one.
We would rather earn the first customers by being useful to people who helped us find the problems.
