FAQ - Questions, answered plainly
The things people most often ask before getting started. If yours isn’t here, get in touch and I’ll answer it directly.
Getting started
- Can you deploy an app I built with Lovable, Replit, Bolt, Cursor, or Perplexity?
- Yes, that’s exactly who I work with. The tool you built it with doesn’t matter. If it’s a web app that people sign into and that stores data, I can get it online safely.
- Why not just use the hosting built into my AI tool?
- Often you should, and I’ll say so if that is where you are. That hosting is one button, it costs very little, and if your app does not hold records the law protects it may be all you ever need. Protected records change the question: your provider has to sign a data-protection agreement, and you have to be able to say where the records are kept and who can reach them. Those are answers about the account your app runs in, not about your app. The longer answer is here.
- What kinds of apps do you support?
- Web apps: something people open in a browser, usually sign into, that stores their information. That covers the large majority of what people build with AI tools. If you’re not sure yours fits, send it over and I’ll tell you honestly.
- Do you need my code, and how do I send it?
- Yes, I need your project files. You don’t need to set anything up first: a zipped folder, or whatever your AI tool exports, is fine. Putting your code somewhere safe and versioned is part of the work I do. The setup guide walks through everything you send.
- Do you use GitHub or Azure DevOps?
- Your code needs to live somewhere that keeps a history of every change and can put updates live for you. Azure DevOps is what I use for that by default. If you’d prefer GitHub, say so and I’ll set you up there instead. Either way the account is yours.
- How long does a deployment take?
- What it costs depends on how much there is to set up: how many parts your app has, which rules apply, and what has to be fixed first. You get a dated timeline in the written plan at the end of the first milestone, before any building begins. You are never left waiting on an open-ended estimate. See how a deployment is delivered.
Cost
- What does the deployment cost?
- A Secure Cloud Deployment starts at $2,500. If your app holds protected records, a Compliance-Ready Deployment starts at $6,000 and adds the written evidence your field asks for. What it costs depends on how much there is to set up: how many parts your app has, which rules apply, and what has to be fixed first. You get one fixed quote before any building starts.
- What is the difference between the two deployment prices?
- A Secure Cloud Deployment gets your app online, secured, backed up, and watched. A Compliance-Ready Deployment does all of that, then proves it. You also get a check against the technical rules your field imposes, evidence that your data is encrypted, a record of who can reach what, and the data-protection agreement your cloud provider has to sign. The engineering is the same in both. What the higher price buys is the written evidence, which is the part you can hand to whoever asks.
- What will cloud hosting cost me each month?
- Your cloud provider bills you directly, and you only pay for what your app uses. Picking the right size is part of what I do, because paying for capacity you never use is the most common way these bills get large. The written plan names every service you will be billed for, so you can price it yourself before you commit.
Security & access
- What access do you need to my cloud account?
- Only what the work needs, and never the level of access that would let me lock you out or change your billing. The exact permissions are listed up front in the setup guide, before you grant anything.
- Is that access safe, and can I revoke it?
- Yes. Every permission is granted to my account from inside yours, so you can withdraw any of it at any time, and all of it the day we finish. Your app keeps running either way. More on how your project stays secure.
- Is my app secure enough to go live?
- Checking it is part of the first milestone, before anything goes live. If something needs fixing, you hear about it in plain language, with what it would cost and whether it can wait. Nothing goes live until you have approved it.
Regulated industries
- Do you work with businesses that have compliance requirements?
- Yes. If you are in legal, financial services, accounting, insurance, or a similar field, your app has technical rules to meet, and how it was built makes no difference to whether it meets them. Every deployment is built that way as standard. Passwords and keys are held in a locked store rather than written into your code. Your staff sign in with a second step. There is a record of who reached what. The database cannot be reached from the public internet. None of these are extras. See how your project stays secure.
- Can I share the handover with my compliance officer?
- Yes, that is exactly what it is for. It covers every account, password, and security setting in plain language, so anyone who needs to check what is in place can read it: your team, a customer’s security reviewer, or whoever reviews you. Here is an example.
- Does this make my practice ready on its own?
- No, and nobody can sell you that. Being ready to meet the rules is not only a technical question. I configure your app and the cloud it runs on to meet the technical rules, and produce the written evidence that it was done. Your written policies, staff training, the person you name as responsible, your ongoing review of what could go wrong, and the statement you sign stay with you. You get that split in writing before we start: what I do and what stays yours.
Ownership & after launch
- Who owns the app and the cloud account?
- You do. Everything is built in cloud accounts in your name: the servers, the place your code lives, and the app itself. I have access while we work together and none after, and nothing stops working when it ends.
- What if I want to leave, or hire someone else later?
- Nothing ties you to me. When your app goes live you receive a written handover covering every account, password, and security setting, so you or whoever you hire next can pick it up without needing to ask me anything. Here is an example.
- Do you offer ongoing support after launch?
- Yes, in two sizes. A daily check on your app is $49/month: I watch it every day, send you a written report each month, and price anything I find before it is done. Keep your app running is the larger one — up to 10 hours a month of hands-on work, with the daily check included — and is quoted per app. The first few months after launch are when most of the questions arrive, so that is usually when it is worth having.
Twenty minutes, and no pitch.
I'll tell you what I'd fix first in what you've built, and why. No pitch.