Resources - Guides and documents for your project
Plain-English answers to the questions owners arrive with: whether the tool you built with can meet the rules of your field, what those rules ask of you, and what a customer’s security review will want to know. Then the documents for your own project.
-
Is Lovable HIPAA compliant?
No build tool is, and none can be. What HIPAA applies to, why the tool that wrote your code is rarely the deciding factor, and what you can check about your own app this week.
Read the guide → -
The FTC Safeguards Rule, for an app you built yourself
What the rule asks of accountants, tax preparers, advisers and insurance agents. Which parts are engineering, which stay with you, and the three things worth doing first.
Read the guide → -
What a customer's security review will ask you
The five questions it comes down to, what a good answer sounds like, and where apps built with AI tools usually come up short. Nobody asks which tool wrote your code.
Read the guide → -
Why your AI-built app gets harder to change
The tool needs more tries, fixing one thing breaks another, and changes that work on your computer won't go live. What's happening, what you can do about it yourself, and how to tell when it is no longer a job for a tool.
Read the guide → -
When to move off Lovable Cloud, and when not to
The built-in hosting is good, and a lot of apps should stay on it. What it is good at, the handful of things that mean it is time to move, and how to tell which one you are.
Read the guide → -
How a deployment works
The three milestones a deployment is delivered in, what you get at each one, and what is included.
See the process → -
A daily check on your app
What gets checked every night once your app is live — that it is up, that its security settings hold, and that nothing it is built on has a publicly known flaw — and what the written report each month is for.
See what it covers → -
What a cloud cost review looks at
Where a cloud bill quietly goes wrong: capacity sized for a launch that already happened, machines that look switched off and are not, and steady work paying the full hourly rate. What I check, and what the written report says.
See what it covers → -
Security & trust
How your app, your cloud account, and your data are kept secure. I take only the access the work needs, and you can withdraw all of it the day we finish.
Read more → -
How access to your work is controlled
For whoever at your firm signs off on outside vendors. Who can sign in to your private client area, what one person can reach, the record kept of every document opened, and what is not audited or certified.
Read the document → -
Azure setup guide
A short, one-time checklist to set up your Azure account and grant the access I need before your deployment begins.
Read the guide → -
Example handover
An anonymized example of the written handover you receive when your app goes live, covering every account, password, and security setting.
View the example → -
Change request process
How changes reach your live app after launch. Write the code yourself or hand the building to me, with a fixed price you approve up front and your sign-off before anything goes live.
See the process →
Twenty minutes, and no pitch.
I'll tell you what I'd fix first in what you've built, and why. No pitch.