Help Center
Deployment

What do you need from me to deploy my project?

Four things — access to the code, fifteen minutes to create accounts in your name, your domain choice, and any API keys your app uses. You never hand over your only copy of anything, and you keep ownership of every account.

Last updated

Four things, none of which require technical setup on your side. The whole handover usually takes one call.

1. Access to the code

Read access to your repository — GitHub, GitLab, or wherever the AI tool left it. If the code only exists as a folder on your laptop, that's fine and common; we'll help you push it to a repository in your account first, which also means you finally have a backup.

You never send us your only copy of anything.

2. Fifteen minutes to create accounts — in your name

Hosting, database, domain registrar, email service. You create them (we'll walk you through each, it's a form apiece), you own them, and you grant us collaborator access that you can revoke any time.

This is deliberate. The most common horror story in this industry is infrastructure registered under an agency's account — every future disagreement becomes a hostage negotiation. We structure ownership so that can't happen, even to us.

3. Your domain decision

If you already own a domain, collaborator access to the registrar. If you don't, pick one and we'll advise on the choice before you buy — the practical notes: the .com if it's available, shorter over cleverer, and matching your business name matters more than keyword stuffing the domain.

4. The keys your app already uses

Whatever API keys the AI wired into your prototype — OpenAI, Anthropic, Stripe, maps, whatever it may be. During deployment these move out of the source code and into environment variables, which is one of the standard localhost-to-production fixes.

Two cautions worth stating:

  • Rotate any key that was ever hardcoded in a file you shared, screenshotted, or committed. We'll flag these during the audit; rotating takes minutes.
  • Check your usage dashboards on those services once you're live. A deployed app can spend real money on API calls in a way a localhost prototype never did — we'll set sensible limits with you as part of the handover.

What you don't need

  • Technical knowledge. Explaining each step in plain language is part of the job.
  • A finished product. Deploying at 80% done is normal; iterating on a live app is usually easier than iterating on localhost.
  • Design assets, copy, or a logo — unless you want that work too, which is a different conversation we're happy to have.
  • Availability. After the first call, most of the week needs nothing from you but the occasional approval.

Ready? Book a free consultation — bring whatever state the project is in. The first four calls booked from this site are free.

Related articles

First 4 calls freeNo obligation

Want us to check this for you?

Book a free strategy call and we'll audit your setup — indexing, robots.txt, schema — and tell you exactly what's blocking you.

Typical response: 24–48 hours. Same day for active engagements.

Didn’t answer your question? Ask us directly — we reply within 24–48 hours.