About
About
A specialised development studio in Faistenau near Salzburg.
OrigoSoft is a development studio in Faistenau near Salzburg. We build web applications, server- and API-side systems and mobile apps — usually where a process still lives in spreadsheets, email and paper forms.
Our clients are rail and bus operators, EU programme authorities, public administrations, industrial companies and associations. What those projects have in common: the software has to stay accountable for years, not merely work in its first one.
How we work
Some of it is the same in every project. The rest belongs in the first conversation — and is set out here so you know beforehand what there is to decide.
What is always true
We deliver in usable parts
Instead of a long build phase with one date at the end, you get finished parts you can use. You see early where it is going and can steer while that is still cheap.
The process first, the software second
We look at how the work actually runs today before discussing features. What is currently solved in spreadsheets and email is the clearest evidence of where it really hurts.
Operable is part of finished
An application is not finished when it works, but when somebody can run it: documentation, reproducible environments, and a restore that has actually been rehearsed once.
We operate what we build
On our own hardware or in your infrastructure. Either way the configuration stays under version control and a rebuild stays traceable.
We do not tie you to us technically
We build on widely used technologies, and the build and the environment are documented and reproducible. Whether the source code is handed over is a matter of agreement; that the project can be continued is not.
What we agree per project
- The length of an iteration
- One week or two, whichever suits the work.
- Access to the repository and the issue tracker
- If you want to follow along or take part, we set it up.
- How the work is billed
- Fixed price, time and materials, or a framework contract.
- Handover of the source code
- Part of the agreement, not of the small print.
- Response time and availability
- Usually set out in the contract once an application is live.
What every build is checked for
These checks run automatically and stop a release when one of them fires — not because checks look good, but because a person reliably forgets them and a machine does not.
Known vulnerabilities in dependencies
Every build compares the libraries in use against the database of known vulnerabilities. If one of them has an advisory, the build does not pass — the decision is then to update it, not to overlook it.
Static security analysis of the code
On server-side applications an analyser looks, on every build, for SQL injection, unsafe redirects and assignments left too far open. Before review, not after it.
Accessibility on every single page
Every page is checked automatically against WCAG 2.1 AA — in every language, at phone and desktop width, in the light and the dark appearance. Zero tolerance for serious and critical violations.
Privacy that is tested rather than asserted
A test makes sure no page calls a domain we do not control and stores nothing on the device unasked. In our own products, deletion deadlines, subject access and anonymisation are features — not paragraphs in a document.
This website is a work sample
It loads nothing from a server we do not control — no typeface, no analytics, no embedded map — stores nothing on your device beyond your theme choice, and therefore needs no consent banner. The colour contrasts are measured rather than estimated, and every page exists in all three languages.
- Projects delivered
- 50+
- Years of experience
- 20+
- Technology areas
- 4