Software worth
owning.

Arcwhin began with a simple belief: useful software doesn't need unnecessary complexity.

That belief shows up as small decisions rather than as a manifesto. Hiras SMS issues one API key, with no scopes, no roles and no expiry, because a single phone with a single key is the honest shape of the problem. It serves on a fixed port and a fixed set of limits, so every copy of it behaves the same way and nothing has to be discovered or negotiated by the code calling it. Choices like that are less impressive on a feature list, and they are the reason the thing is still simple to explain a year later.

Every product starts with a real problem. Most ideas never become products. The ones that do are built with care and released when they're ready, not because a roadmap says they should be.

Every product begins as an experiment. Only the ones that prove their value become part of Arcwhin.

An experiment is allowed to fail quietly. It gets built far enough to answer one question, which is whether anyone is genuinely better off with it than without it. When the answer is no, the work is set down instead of being dressed up and shipped anyway. Nothing much is lost by that. What would be lost, over a few releases, is the meaning of the name on the things that do come out.

That's the whole idea. Arcwhin isn't a studio chasing volume, and it isn't a consultancy selling hours. It's a publisher: a small, deliberate collection of software that earns its place by being genuinely useful.

What independent publishing means here

Independent describes the constraints, not a badge. There is no outside investor to satisfy, no growth figure to hit by a given quarter, and no sales conversation that ends with a feature being promised to close it. The catalogue can therefore stay small on purpose, and a product can take the time it actually needs without anyone having to justify the delay to someone counting.

It also means the responsibility doesn't move anywhere. Putting something out under the Arcwhin name is a commitment to answer for it: to fix what breaks, to explain what it does, and to keep the description of it accurate even when a vaguer one would be easier to sell. That is the difference between publishing software and simply uploading it.

The standard

The standard behind everything here is quiet but firm: a product ships when it's dependable, or it doesn't ship. Documentation is part of the work, not an afterthought. Privacy is a default, not a setting.

Dependable is a specific bar rather than a feeling. The software has to do the thing it claims, keep doing it while nobody is watching, and behave predictably when the network, the battery or the person using it does something unexpected. It has to be honest about the cases it can't handle rather than hiding them behind a spinner. And it has to be finished in the unglamorous places, which is usually where unfinished software gives itself away: the error messages, the empty screens, the second launch.

The same bar applies after release. A product isn't done at the download. It's done when somebody else can install it, understand it, and get out of it what they came for without having to ask us first.

Documentation and privacy are part of the product

Both are usually treated as extras, which is a fair part of why both are usually poor. Documentation gets written once the software has already shipped, by someone reconstructing decisions from memory. Privacy gets added as a settings screen, which quietly makes the less careful behaviour the default for everyone who never opens it.

Here they're part of the build. Documentation is written alongside the software, which also turns out to be the cheapest design review there is: an option that can't be explained in a short paragraph is usually an option that shouldn't exist. Privacy is decided at the same time as the feature it belongs to, by asking what that feature actually needs and taking only that. The result is meant to be unremarkable. You should be able to read what a product does, believe it, and not have to go hunting for what the page didn't say.

If Arcwhin does its job, you won't need to be sold anything. You'll simply notice that the things it makes are considered, and decide to keep an eye on whatever comes next.