Web applications
Multi-user products with accounts, orders, balances and an admin side. Money paths are written first and tested hardest.
CAPABILITIES
What we write, what we ship, how it runs.
Nothing on this page is aspirational. Every language is one we work in, every kind of project is one we have delivered, and the process below is the one you get.
Languages
- Python
- Application servers, payment and provider integrations, scheduled jobs, data cleanup scripts.
- JavaScript
- Everything that moves in a browser: canvas and WebGL scenes, live dashboards, form logic. Written plain, no framework tax.
- PHP
- Endpoints and CMS work on shared hosting, where a long-running process is not an option.
- SQL
- Schema design, migrations, reporting queries and the audits that prove a number on a dashboard is real.
- HTML
- Semantic document structure, which is also what search engines and answer engines read.
- CSS
- Layout, type systems and motion. Hand-written, no utility framework.
- Bash
- Deployment, backups, log analysis and the small tools that keep a server honest.
What we ship
Marketing sites
Fast, hand-built pages with a real content model behind them rather than a page builder.
Integrations
Payment gateways, crypto settlement, third-party APIs, webhooks. Signed, verified, and never trusting the caller.
Automation
Scheduled jobs that watch a system and report when something drifts: pricing, stock, indexing, uptime.
Search visibility
Structured data, sitemaps, internal linking, and measurement of what crawlers actually fetched.
Interface and motion
Design systems, typography, canvas and WebGL work, all measured against performance and accessibility budgets before handover.
What it runs on
- Linux
- Every production box we run.
- Caddy
- TLS and reverse proxy, certificates renewed without anyone touching them.
- systemd
- Process supervision, timers, restarts that survive a reboot.
- Cloudflare
- DNS, proxy, caching and origin protection.
- SQLite / PostgreSQL
- SQLite where a single box is enough, PostgreSQL where it is not.
- Gunicorn
- Serving Python applications under load.
Projects
Client work is described by sector, never by name.
-
Social media platform
Three times the orders, same hardware
Throughput went from 1.0 to 3.0 orders per second.
Python / Flask / PostgreSQL / Caddy
-
Marketplace
From invisible to 1,600 indexed pages
Indexed pages reached 1,660 and daily clicks rose from 6.7 to 12.4.
Technical SEO / Structured data / Log analysis
-
Subscription service
The sign-in form was 778px below the fold
Form reaches the first screen on a 390px viewport with no horizontal overflow.
CSS / Headless Chrome / Puppeteer
How a project runs
- 01 Pick and pay You choose a package at its published price and pay. There is no call to get a number, because the number is already on the page.
- 02 Brief A short form opens once payment clears: what it is for, who it is for, what you already have. Ten minutes, not a workshop.
- 03 Build Work starts on the next working day. You talk to whoever is building it, not to an account manager.
- 04 Review You see it on a real URL, not in a slide. Each package states how many revision rounds it includes.
- 05 Verify Performance, accessibility and responsive behaviour are measured and the numbers go to you with the handover.
- 06 Hand over Code, access and ownership transfer to you. We keep the right to describe the work without naming you.
How we work
Tests before code
A failing test comes first, then the smallest change that passes it. This site was built that way and ships with its own suite.
Verified in a real browser
Pages are opened headless at phone and desktop widths and measured for overflow, contrast and touch targets. Not eyeballed in a preview pane.
Nothing derived
If we did not measure it, the field stays empty. No invented percentages, no rounded-up case study numbers.
Money paths are paranoid
A payment callback is a nudge, never proof. Status comes from our own signed query against the provider.