AI can build software. It can’t run your studio.
Tools like Lovable, Replit, Cursor, and Claude Code can turn a prompt into a working website in an afternoon, and some will host it for you. That is software. A photography business is everything that happens after the demo works: private galleries, original files, payments, consent, email, and someone who answers when something breaks.
Four jobs after launch
What a site still needs once it’s built
Build
The part AI does best: layout, copy, animation, and a first working version in hours.
Run
Hosting, security fixes, backups, monitoring, and a bill that stays predictable. Someone is on call, and it’s now you.
Protect
Private client galleries, payments, consent, and email delivery. A site can look finished while any one of these is broken.
Exit
Owning the code is not the same as owning a portable library of masters, URLs, and client access you can take with you.
Two kinds of tool, one gap
Both kinds write real code. Neither one operates it.
Hosting is no longer the missing piece. Operating is.
| Type | Examples | What it does | What still falls to you |
|---|---|---|---|
| App builders | Lovable, Replit, Bolt, v0 | Generate an app and host it for you | Security review, data access rules, backups, ongoing cost, leaving |
| Coding agents and editors | Cursor, Claude Code | Write and edit code in a project you own | All of the above, plus hosting, domains, and deployment |
What “looks finished” leaves out
Access control. The most common serious flaw in generated apps is missing or broken authorization: the rules about who may read which record. For a photographer, that is a private gallery that opens when someone changes a number in the address. A site can pass every visual check and still fail this one.
Secrets and backups. Keys end up in the wrong place, and databases run without a backup anyone has tested. Both stay invisible until the day they matter.
Patching. Frameworks, libraries, and server runtimes receive critical security fixes several times a year. Someone has to notice and apply them.
Instructions are not permissions. Telling an agent “don’t touch the database” is a request, not a rule. In 2025, Replit’s agent deleted a live production database during a code freeze it had been told to respect. Permissions, separate environments, and tested backups are what make that survivable. A chat message isn’t.
Images and search. Originals, web derivatives, color profiles, lazy loading, canonical URLs, sitemaps, and redirects all have to be asked for, built, and maintained. A prompt gets exactly what it describes.
The cost curve
The sticker price is the starting point. Heavy build sessions use up included credits quickly, usage-based billing takes over, and the extras arrive one at a time. In one widely reported case, a plan that looked like $25 a month produced a bill of several hundred dollars in a few days of heavy agent use, because the credits ran out and pay-as-you-go began.
Typical monthly cost for a working studio site, as of October 2026. Ranges vary by tool and use.
| Stage | Typical monthly cost | What’s behind it |
|---|---|---|
| On the pricing page | $20 to $30 | One tool subscription with limited credits |
| During an active build | $50 to $150 | Extra credits, hosting, a database |
| Live with clients | $100 to $350 and up | Image storage and delivery, email sending, error monitoring, a domain |
The larger cost is hours. At 9 p.m. a client tells you their gallery link stopped working. Nobody else is going to look at it.
Where these tools earn their place
They are strong for prototypes, custom design experiments, a campaign landing page, and small scripts that batch rename, convert, or sort files. They also suit technical photographers who want to own the code and have a maintenance plan. The test isn’t whether the tool is good. It’s whether you want the job it leaves you.
A two-question test
Could you restore the whole site tonight if the host disappeared? Can you say, for any client gallery, exactly who can open it and why? If either answer is no, you are hosting a demo, not running a studio.
Build on a platform that already runs the operations
ArtInStack’s job is the running part: one media library with your site and portfolio on the same library, private client delivery, a custom domain with HTTPS that renews itself, and the sitemaps, canonical URLs, and redirects that keep pages findable.
You can still build custom things with AI. ArtInStack also has a Developer API, so those tools can connect to the platform instead of replacing it.
Software takes an afternoon to generate. A studio has to keep working on Monday.
Build with AI. Run on a platform.
Generate a draft wherever you want. Keep media, delivery, and the right to leave on a platform that already runs the operations.
Also in Guides: Where to draw the line with AI in photography · Can AI build a photography website? · Can ChatGPT replace a CMS?