Why ask me for your project
One developer. The whole stack.
Already running.
Most projects are passed between a designer, a developer, a hosting company and whoever is on call when it breaks. Here it is one pair of hands from the first sketch to the server it runs on - and you can see that server answer, below, right now.
Every layer, one pair of hands.
Tap a layer. At an agency each one is a different person, a different ticket and a different invoice. Here they are all mine, and they already run on my own rack.
This page comes off the software I wrote.
joshtified.com is served by PlayPort, the Windows panel I built, from one machine in a rack in the Netherlands. Ask it: the numbers below are measured by your browser, not typed in.
How long this server takes to answer your browser. Press to measure again.
Game servers, websites and mail, from one PlayPort install. The live stream page answers from the same machine.
Netherlands (CET). You get an answer from a person in this time zone, in Dutch or English.
Pick what you need. See how it would go.
Three steps, the same every time: I look at what you have, you get a fixed quote, it ships and stays up. The details change with the project - pick yours.
Write now, and this is when I answer.
Mail is read by me, in the Netherlands, usually within a working day. The timeline is worked out from the clock right now, not a promise copied from a template.
Three questions, then your message is already written.
Answer honestly. The text below is built from your answers; change anything, then send it. It lands in my inbox with your address as the reply-to.
Tell me about it.
Pick the three answers above and the message writes itself.