HOW WE BUILD / KEYS INCLUDED
Opinionated about technology. Not about keeping you hostage.
We build on a deliberately small stack, put the important accounts in your name, and hand over software you can inspect, operate, and take elsewhere.
01 / OWNERSHIP FIRST
We make our living building software you’ll want to keep. Not making it difficult for you to leave.
Plenty of agencies build inside their own accounts, then promise a transfer someday. We reverse that. For substantial projects, you establish the domain, accounts, and billing relationships first, then invite us in. Ownership is a starting condition, not a closing argument.
Not eventually. The domain, repository, hosting, billing, and data live in accounts your business controls from the start.
We get the permissions the work needs. Elevated setup access is deliberate, documented, and reduced when it is no longer needed.
Source, tests, deployment notes, and access are organized so another developer can continue without asking our permission.
02 / THE STACK
Performance, low maintenance, portability, automation, and operating costs that make sense. Not a services menu we’re trying to sell.
Reviewed commits · automated tests · CI/CD
DNS · Workers · storage when needed
Model access only when the application itself needs AI
HOSTING & INFRASTRUCTURE
Our default for modern websites and many business applications: DNS, HTTPS, Workers, static assets, security, and performance. We add D1, R2, or another service when an actual requirement justifies it, not because the platform offers it.
Keep domain registration wherever it is. You do not need to transfer a domain to Cloudflare to work with us.
SOURCE & DELIVERY
Your code, full history, tests, and deployment automation live in a repository your business owns. Production ships from a reviewed commit through GitHub Actions. Changes stay inspectable and releases reproducible, instead of mysteriously appearing from somebody’s laptop.
If our access ends, the repository, its history, and the ability to deploy remain yours.
AI ACCESS, WHEN NEEDED
When an application needs AI, we usually start here: one API across multiple model providers, with room to trade capability against cost as requirements change. It reduces coupling to a single model vendor; it does not make every model interchangeable.
Not required for an application without AI features. We do not add an AI dependency to make a project look modern.
03 / THE ENGINEERING ADVANTAGE
The machines do the heavy lifting.
We make sure they’re lifting
the right things.
AI helps us cover more ground without pretending experience is optional.
It accelerates exploration, implementation, and the repetitive parts of development. It does not choose the architecture, approve the security model, accept the test result, or decide that something is ready to ship. Those stay with an experienced human.
Faster exploration and implementation, with fewer hours consumed by boilerplate.
Less repetitive overhead means more engineering attention where it actually matters.
Architecture, security, testing, and release decisions remain deliberate human calls.
Working software tested against the problem. Not a pile of generated code and a hopeful expression.
Two different kinds of AI. We use AI-assisted engineering to build your software. Your finished application only needs OpenRouter, or another AI API, if the application itself has AI features. You do not need an AI subscription because of how we work.
04 / OPINIONATED, NOT INFLEXIBLE
Our stack is a default, not a doctrine.
If a small WordPress repair needs a small WordPress repair, we won’t turn it into a Cloudflare Workers migration. If a serious application genuinely needs PostgreSQL, AWS, or another platform, that is what it should have. We evaluate the system you have and the requirement in front of us before recommending a rebuild.
Existing infrastructure stays unless it is the source of the problem. A repair should not become a platform referendum.
We look at what is there, what it costs, and what it prevents. Changing platforms is not a strategy by itself.
A rebuild is a chance for fewer moving parts and clearer ownership. Not a chance to add every shiny object.
We won’t stage a migration just to make our preferences feel important.
05 / BEFORE WE BUILD
You set up the accounts. We take it from there.
This is less dramatic than it sounds. For a substantial project or rebuild, the first job is making sure your business owns the foundation. We confirm what your project actually needs during scoping; not every service or permission is required every time.
Your domain and business email should live in accounts you control. Keep registrar access, recovery details, and two-factor authentication. You can register a new domain or keep the one you have; transferring registration is not a requirement. Cloudflare Registrar is one option.
Create or use a GitHub account or organization and a Cloudflare account with your business email and billing. OpenRouter is optional and only enters the picture when the application needs AI. You pay providers directly.
Official signup: GitHub Cloudflare OpenRouter
Invite us with the roles and repository permissions appropriate to the work. Elevated access may be needed during initial setup, but it is deliberate and revisited afterward. Never send passwords, recovery codes, or API tokens through ordinary email.
Provider help: Invite a GitHub member Manage Cloudflare members
Work lands in your repository as reviewable commits. Automated checks run. Production deploys from the validated commit through GitHub Actions, so the live version traces back to a specific change. We document how to build, test, deploy, and operate it.
You retain owner access throughout the engagement. Removing our access is straightforward, and a real transition also rotates credentials created during the work. The repository, tests, and deployment notes should let the next developer build and deploy without us.
Provider help: Remove a GitHub member Manage GitHub tokens Manage Cloudflare API tokens Manage OpenRouter keys
THE NEXT MOVE IS YOURS
We bring the engineering experience, the AI-powered workflow, and a practical plan. You keep the keys.