FAQ

One price for the whole of the work you described, agreed in writing before anything starts, and it does not move unless you change what you asked for. The services page carries the published prices and pricing explains how they are arrived at.

It depends on the work, and you get a date with the quote rather than after it. What does not happen is a quiet overrun: the repository is public from the first commit, so progress is a thing you look at rather than a status we report. Process describes the whole run.

What the thing has to do, who uses it, and what it has to talk to. Text and pictures can arrive later; the decisions cannot. Half an hour on contact is usually enough to find out whether we are the right people for it, and hearing that we are not is a normal outcome.

Your content, your data, your domain and your credentials are yours and always were. The code is published under an open licence, which gives you every right that matters in practice: run it, change it, hand it to another developer, keep it running without us. Nothing has to be bought back later, and licenses lists the exact terms.

No. Everything built here is published as open source, and agreeing to that is the condition of working with us. There is no version with an exception, a private repository, or a delay until later. The public repository can live under your own GitHub account or under ours; we recommend ours, where it sits beside the packages it is built from and goes through the same checks as everything else we run. Your content, your data and your credentials stay private; the code that runs them is public. Philosophy explains why that line sits where it does.

You, us, or anybody else you choose. Maintenance is optional and priced on its own, and nothing is held back to make it necessary. If you take the whole thing to another developer, the licence already allows it and the code is already in your hands.

Anything built for a browser works wherever a browser does, including on Windows and on a Mac. Desktop software written here runs on Linux and is not ported, at any price. Philosophy explains why, and standards states it as a requirement rather than a preference.

A program, not a promise. Types have to check, a discipline tool has to approve the shape of the code, the verification scripts have to run, and the whole thing has to build; work that fails any of them does not land. Standards lists what every change has to pass and handbook describes how the work is built and released.

Nothing of yours goes with it. Everything is already published under a licence that cannot be withdrawn, on other people's disks, and your own copy keeps working whether this organization exists or not. Governance says who maintains what while it does exist.

No analytics, no advertising pixels, no behavioural profiling and no third party watching the reader on anything the organization runs. The cookie policy lists what a browser stores, and it is short for that reason.

What you send and what a server has to process to answer a request, and nothing gathered on the side. The privacy policy names each one, how long it is kept, and how to ask for it back or have it deleted.

Yes, under the licence of the repository it came from, without asking and without owing anything. What the licence does not grant is the name: presenting your work as Trebired, or as endorsed by it, is the one thing it does not allow. Brand and the trademark policy say exactly where that line is, and contribute covers sending something back.