Services
Bring a problem. Leave with a plan, then the system.
Fopull builds custom software for businesses end to end: the scope, the design, the build, the deploy and the running of it, by the same engineer throughout. The stacks below are evidence, not a menu.
How an engagement goes
The same four steps whatever is being built. Stop after any of them and keep what it produced.
-
A scope call
Thirty minutes on the problem and the constraints: deadline, stack, compliance, budget. If it is not a fit, you hear that on the call.
-
Short paid discovery, then a written plan
What gets built, in what order, what it costs, what it runs on, what could go wrong. Written so you can take it to anyone. Most projects are then fixed-bid milestones; open-ended research and ongoing maintenance are hourly.
-
Built in milestones you sign off on
The running system is visible from the first milestone. Every migration is verified before it touches your data and every deploy is scripted.
-
Handed over with a runbook, or run for you
Source, infrastructure, tests, documentation and the operating notes written during the build. A maintenance retainer if you would rather Fopull kept running it.
Things Fopull has built, by kind
Each page below is written for one kind of problem, with a system from our own production as the worked example. None of them is the only thing Fopull does.
-
Custom web applications Laravel · PHP 8.3 · PostgreSQL · Blade · Alpine.js
A business system that other people depend on: accounts, roles, records, money, and the boring middle that makes it hold up for years. Built in Laravel on PostgreSQL, server-rendered, and handed over with the documentation to run it.
-
Backends, APIs and integrations REST · OAuth 2.0 · PKCE · Stripe · Webhooks
The part of a system nobody sees and everybody depends on: the API a client talks to, the webhook a payment provider calls, the integration with the tool your business already runs on. Designed on the assumption that the network is hostile and the client is wrong.
-
HIPAA-adjacent systems BAA · Audit logging · Encryption at rest · RBAC · Strict CSP
Intake portals, scheduling, records that sit next to protected health information. Built under a Business Associate Agreement to your security officer's controls, with the audit log, the encryption and the access model in place before launch rather than bolted on for the audit.
-
Game backends and real-time systems Unity · C# · Laravel · Reverb · UDP relay
The backend a game needs to be real: sign-in from a client that cannot keep a secret, saves the server owns, an economy that reconciles, matchmaking over websockets, and multiplayer that works from two home connections. All of it runs in production at Fopull, for three different games.
-
Self-hosted infrastructure Linux · Proxmox · Apache · PHP-FPM · PostgreSQL
Linux servers you own, set up and hardened so nothing listens on the public internet, backed up in a way that has been restore-tested, and handed over with the runbook. Or operated for you. Either way you know where the data is.
Written from the work
Engineering guides tagged to client work: real configuration, real decisions, from systems Fopull runs.
-
Real-time multiplayer with Laravel Reverb
Running two live multiplayer games on Laravel Reverb: channel design for hidden information, the ShouldBroadcastNow trap, and the systemd setup.
-
OAuth 2.0 and PKCE for a Unity game client
A complete authorization-code-with-PKCE login for a Unity game: the deep-link handling desktop and mobile each need, and what the server must enforce.
-
Self-hosting behind a Cloudflare Tunnel
A production stack online with no open ports and no static IP: the ingress rules for websockets and subdomains, and four things that catch people out.
Start with the problem
Describe what you are trying to do and what is in the way. Rough notes are fine. A reply from Ty within one business day.