Refaktr

Take your Lovable app to AWS.

Analyze your Lovable project and generate an AWS deployment kit for supported apps—in infrastructure you control.

Analyze Project → View on GitHub →

Open source · A Refaktr project

Analyze your project

Upload a .zip of your Lovable project. Prodify inspects it and generates a CloudFormation template you deploy into your own AWS account.

Drop your .zip here

or click to browse

Generates a CloudFormation template

How it works

01

Connect GitHub

Enable GitHub integration in Lovable.

02

Export

Download the repository as a ZIP from GitHub (Code → Download ZIP).

03

Analyze

Upload the ZIP here. Prodify inspects the project and writes a template.

04

Deploy

Launch the generated stack in your AWS account from the console.

05

Open

Visit the CloudFrontURL in the stack's Outputs tab.

Compatibility

Prodify reads the project you upload and decides how to prepare it.

Works today

  • Node projects with a build script that outputs dist/ or build/ — the Vite + React setup Lovable generates
  • Projects that already include a built dist/ or build/ folder, uploaded as-is
  • Plain static HTML, CSS, and JavaScript with no build step

Needs a local build first

  • Builds that take longer than 10 minutes
  • Builds requiring credentials, private registries, or environment variables at build time
  • Anything whose output doesn't land in dist/ or build/

In these cases, build locally and upload the output folder instead.

What Prodify supports

Project analysis

Detects whether the upload needs a build, is already built, or is plain static files.

Build execution

Runs bun run build, falling back to npm ci and npm run build.

Client-side routing

403 and 404 responses fall back to index.html, so SPA routes resolve.

Private origin

The S3 bucket blocks all public access and is reachable only through CloudFront.

HTTPS by default

Viewer requests redirect to HTTPS on the CloudFront distribution domain.

Content upload

A custom resource publishes the built assets into the bucket during stack creation.

What gets generated

One CloudFormation template you can read before you deploy it. Every resource lands in your account.

Resources

  • AWS::S3::Bucket private, all public access blocked
  • AWS::CloudFront::Distribution HTTPS, SPA error routing
  • AWS::CloudFront::OriginAccessControl SigV4 origin signing
  • AWS::S3::BucketPolicy scoped to that one distribution
  • AWS::IAM::Role deployer role scoped to the bucket and its logs
  • Custom::ContentDeployer uploads your built assets

Outputs

  • CloudFrontURL the HTTPS URL your app is served from
  • S3BucketName the bucket holding your build output

The template is plain YAML. Keep it, diff it, or fold it into your own infrastructure repo.

Architecture

What the generated stack looks like once it's deployed in your account.

Deployed in your AWS account

Limitations

Prodify v1 focuses on frontend deployment. It does not automatically migrate your database, authentication, storage, server functions, or application data.

Not handled

  • Backend services your app calls stay where they are
  • Environment variables and secrets are not migrated
  • Custom domains and certificates are not configured

Worth knowing

  • Your app keeps talking to its existing backend after deployment
  • Generated stacks are a starting point, not a finished platform
  • Read the template before deploying it — that's the point of generating one

Why I built it

I kept hitting the same wall: AI tools get you a working app in an afternoon, and then the app lives somewhere you don't control, described by infrastructure you can't read.

Prodify is the smallest useful step out of that. It doesn't move your whole system — it takes the part that's genuinely portable, the built frontend, and hands you infrastructure as code you own and can inspect. Everything it can't do is listed above rather than glossed over.

That's the same question the rest of Refaktr asks: the prototype works, so what does it actually take to run it somewhere real?