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 Replit, Bolt, Lovable, Cursor, or v0?
- Yes, that’s exactly who I work with. The tool you used to build your app doesn’t matter. As long as it’s a standard web app, I can get it deployed safely on Azure.
- What kinds of apps do you support?
- Standard web applications: a web frontend and backend with a database. That covers the large majority of apps 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 to deploy them. You don’t need GitHub or any version control set up first; a zipped folder or an export from your build tool is fine, and I set up your code repository for you as part of the work. The setup guide walks through everything you send.
- Do you use GitHub or Azure DevOps?
- Azure DevOps is my standard platform for storing your code and automating deployments, so it’s what I’ll use by default. If you’d prefer GitHub, just let me know, and I’m happy to set you up there instead.
- How long does a deployment take?
- It depends on how complex your app is. You get a clear timeline as part of the implementation plan in the first milestone, before any work begins. See how a deployment is delivered.
Cost
- What does the deployment cost?
- A Secure Azure Deployment starts at $1,500, with the final price depending on how complex your app is. You get a clear quote up front in the implementation plan, with no surprises.
- What will Azure itself cost me each month?
- Azure hosting is billed by Microsoft directly, and you only pay for what your app actually uses. Choosing the right services is a big part of the value I add: I assess your project and pick the most cost-effective setup for what you actually need, instead of over-provisioning. Once your implementation plan is set you’ll know exactly which services those are, and you can price them yourself with Microsoft’s official Azure Pricing Calculator.
Security & access
- What access do you need to my Azure account?
- Only the minimum needed to do the work, never Owner or full admin. The exact roles are listed up front in the setup guide, so there are no surprises.
- Is that access safe, and can I revoke it?
- Yes. Every role is granted to my account and stays in your control. You can remove it at any time and revoke all of it the day the project ends, with your app unaffected. More on how your project stays secure.
- Is my app secure enough to go live?
- Reviewing your app for security issues before anything goes live is part of the first milestone. If something needs fixing before launch, you’ll know in plain language, not after the fact.
Regulated industries
- Do you work with businesses that have compliance requirements?
- Yes. If you’re in legal, financial services, accounting, insurance, or a similar field, your app usually needs specific controls to meet regulatory requirements—and an audit won’t care that you built it with an AI tool. I build every deployment with those controls in mind: credentials stored in Azure Key Vault (not in your code), multi-factor authentication, access logging, and private networking for databases. These aren’t add-ons; they’re part of how I deploy by default. See how your project stays secure.
- Can I share the handoff documentation with my compliance officer or auditor?
- Yes, that’s exactly what it’s designed for. The handoff document covers every resource, secret, and security control in plain language. It’s meant to be handed to anyone who needs to verify what’s in place—your team, a regulator, or an auditor. Here’s an example handoff.
Ownership & after launch
- Who owns the app and the Azure account?
- You do. Everything is built in your own Azure account, in your name: the infrastructure, the code repository, and the app itself.
- What if I want to leave, or hire someone else later?
- There’s no lock-in. At go-live you receive a complete handoff document covering every resource, secret, and control, so you or anyone you hire can take over. Here’s an example handoff.
- Do you offer ongoing support after launch?
- Yes. Ongoing feature development, fixes, and maintenance are available separately once your app is live, so you have someone to call as your business grows.
Ready to get your app moving?
Tell me what you’ve built and where you’re stuck. I’ll get back to you within one business day.