Sponsor an integration
Endstate already reinstalls applications through WinGet and Chocolatey. Integration sponsorship funds deeper migration support: safe settings capture and restore, version handling, package-identity edge cases, testing, and documentation.
Request a quoteThe distinction
Installation
Package installation is a solved problem, and Endstate already uses it. Point it at a package identity and the application arrives on the new machine, at the version the package feed serves, configured exactly as its own installer leaves it.
Migration support
Migration support is the part that is not solved. It means knowing which files and registry keys hold the settings that matter, which of them are safe to move and which are machine-bound, licence-bound, or contain credentials that must never be copied.
It means handling the shape those settings take in different versions and editions, reconciling package identities that differ between feeds or change under the project’s feet, then testing the round trip on a clean machine and writing down what it does and does not cover.
That work is specific to each application, and it is what a sponsorship pays for.
A narrow promise
Ordinary Endstate development continues regardless, and so do community contributions — anyone can open a pull request for an application module, and sponsorship does not close that door or move anyone else down a queue they were promised a place in.
What a sponsorship buys is narrow and concrete:
01
The work is scheduled and done, rather than waiting for the application to reach the top of the list on its own.
02
The quote names the settings, versions, and editions covered, and says what is out of scope, before any money changes hands.
03
The integration is tested end to end on a clean machine, and the result is documented.
It does not buy influence over the rest of the roadmap, a support contract, or any change to the free product, which stays free and complete either way.
Public work
A sponsored public integration becomes part of Endstate itself: open source under Apache 2.0, in the public module catalogue, and available to everyone at no cost. You are funding work that is given away, and the application’s other users benefit from it too.
Private work
Private organisational and vendor integrations — for internal line-of-business software, or for a vendor who does not want a public module — are available by quotation and are handled separately.
Maintenance boundaries
A sponsorship is delivered work, not a maintenance commitment. When it is complete, the integration exists, is tested, and is documented. It does not come with lifetime maintenance, and applications change: a vendor can move a configuration file, restructure a settings format, or change package identity at any time, and a working integration can stop working through no fault of either side.
Ongoing compatibility guarantees are a different thing and require a separate agreement. If you need an integration to keep working against future releases, say so in your enquiry and we will scope that explicitly rather than leave it implied.
Request a quote
There is no public price, because there is no standard job — an application with two settings files and one package identity is not the same work as one with per-edition registry layouts and a licence blob that must not be copied. Send the details below and you will get a scope and a price.
The link below opens your email client with those questions already in the body — fill in what you know and send it. Nothing is stored anywhere until you reply.
Request a quoteWhat to include
Prefer to support the project in general rather than one application? Support Endstate.