Available for new builds — Q3 slots open
I'm Axion Bayes — an independent developer shipping custom sites, web apps and the infrastructure under them. Domains, VPS, SSL, deploys, backups: handled end to end, not left as "you'll need a hosting guy for that."
Web development is the current focus. Everything around it — the server, the certificate, the pipeline — comes with it when you need it.
Marketing sites, portfolios and company sites built by hand. Semantic markup, real performance budgets, content that a search engine and a human both understand.
When a site needs to remember things: accounts, roles, data, payments, APIs. Built as a real application with a database and a migration path — not a pile of scripts.
Product catalogues, carts, checkout, appointment slots and deposit flows. Payment provider wired in, order notifications reaching you where you already look.
The part most quotes leave out. I buy or transfer the domain, point DNS, provision the VPS, harden it, terminate TLS, set up backups and one-command deploys.
Existing site too slow, too fragile, or stuck with a host you can't reach? Audit, plan, then move it — without downtime and without losing your rankings.
Updates, monitoring, uptime alerts, small content changes and an incident channel. Month to month, no lock-in, cancel whenever.
Every project runs the same track. You always know what stage we're in and what happens next.
30 minutes. What the site must do, who it's for, deadlines, anything you already own (domain, hosting, logo, copy).
A written plan: page list, features, stack choice, infra needs, timeline and a fixed price with the payment split. You approve in text before I start.
Work in weekly increments on a private staging URL you can open any time. Feedback lands in a tracked list, not a forgotten chat message.
Cross-browser and device pass, accessibility and performance checks, then the repo, credentials and a written runbook handed to you.
DNS cutover, monitoring confirmed, and 30 days of post-launch fixes included. Optional retainer afterwards if you want me on call.
Price tracks two things: how much site there is, and how much infrastructure it needs. Set the controls below for a working range — the real number is fixed after the scope call.
from —
One to three screens. Single clear goal: portfolio, launch page, campaign site, personal brand.
from —
Four to eight pages with real content structure — services, work, team, careers, blog, contact.
from —
Transactions or reservations. Product data, availability, payments, and the notifications that keep you informed.
from —
Software with users and state: dashboards, portals, SaaS cores, internal tools, API-backed products.
Already have the site and just need the plumbing? These can be bought on their own.
| Task | Includes | From |
|---|---|---|
| Domain & DNS | Registration or transfer, A/AAAA/CNAME/TXT records, registrar access handed to you | — |
| VPS setup | OS hardening, SSH keys, firewall, nginx/Caddy, TLS auto-renew, log rotation | — |
| Deployment pipeline | Git-based deploys, staging branch, one-command rollback | — |
| Email on domain | MX/SPF/DKIM/DMARC for Google Workspace, Zoho or self-hosted | — |
| Performance audit | Core Web Vitals report, prioritised fix list, before/after numbers | — |
| Retainer | Patches, monitoring, content edits, priority channel — per month | — |
I pick the smallest stack that will still be maintainable in three years. You get the reasoning, not just a logo wall.
// rule of thumb
A brochure site does not need Kubernetes. A booking system does need a database and backups. I'll tell you which one you're buying before you pay for it.
Because two "five-page sites" are rarely the same job. One is static text; the other has a booking calendar, payments and an admin panel. Pricing at the lower end of the first and the upper end of the second would mean overcharging half my clients. So: the tier sets the base, pages and features scale it, and infrastructure is itemised as its own line.
Anything beyond writing the code and publishing it: registering or transferring a domain, pointing DNS records, provisioning and hardening a VPS, issuing and renewing TLS certificates, setting up email on your domain, building a deployment pipeline, wiring a payment gateway, or migrating content off an existing host.
No. If you already own them I'll work with what's there and hand back the configuration. If you don't, I'll set them up under your name with your payment method so you keep ownership. Nothing gets registered inside my account.
Fifty percent to start, fifty percent on launch. Larger web apps are split into milestones tied to delivered features. Third-party costs — domain renewals, server rent, paid fonts — always appear as line items at cost before anything is purchased.
A landing page is usually 4–7 days. A business site 2–3 weeks. A store or booking system 3–5 weeks. A custom web app 5–9 weeks depending on integrations. The estimator gives a live figure, and the timeline is confirmed in writing before work starts.
Thirty days of fixes are included after launch — bugs, browser quirks, small copy edits. After that it's either an hourly rate or a retainer, whichever suits you. You're never locked in: the code, the server and every account are in your name.
Yes, and it's a common request. I start with an audit of the current site — speed, structure, what's ranking, what's broken — then propose either a rebuild or a targeted fix list. Migrations run on staging first so there's no downtime.
Send the shape of it — what the site needs to do, roughly how many pages, whether you already have a domain, and your deadline. You'll get a written reply within 24 hours with an honest range and the next step.