Building for the web since 1995, from hand-written HTML to cloud infrastructure. Whatever the problem turns out to be, the odds are I have met it before.
Websites and bespoke software, WordPress and WooCommerce, hosting and AWS, data and reporting, integrations, and AI where it genuinely earns its place.
A site is not finished when it launches. Hosting, updates, backups and the day something breaks can be my problem instead of yours.
I built my first website in 1995. The web was new, everything felt possible, and I have not really stopped since.
What hooked me was never any single technology — it was working out how things fit together, and what to do when they don’t. Thirty years later that has covered websites and bespoke software, servers and cloud migrations, databases and reporting, and the automation that saves somebody a day a week.
The work arrives in every shape. A shop whose checkout is too slow. A charity with data in five places and no way to report on it. A business that has outgrown the spreadsheet holding it together. Whatever it is, the first job is working out what is actually wrong.
I am not precious about the size of it either. Some of the most useful things I have done took an afternoon.
Tardix is where I do this. Tell me what is getting in your way and I will tell you straight whether I can help and what it would take.
Albert Sola
No jargon, no ten-page proposal, and no pretending a small job is a big one. You tell me what is going wrong or what you want to build, and I tell you plainly what it would take — or that you don’t need me for it.
Most of it starts as a short conversation rather than a proposal. If you are not sure whether something is even worth spending money on, that is a good enough reason to ask.