What rwaft can't do yet
rwaft builds websites and front-end apps that run in the browser. Here's what that rules out today, and the usual way around each.
No back end
- No database: an app can save data in the visitor's browser, but it won't sync between devices or people
- No logins or accounts
- No payments: link to a checkout you already use, like a Stripe payment link
- Forms don't save or send what visitors type: link to a form service like Google Forms or Tally
Files and hosting
- You can't upload images or files yet: use links to images that are already online
- Every site is public to anyone with its link
- No custom domains yet
- Up to five pages per site
- A site's code is kept for a day after each build; after that, describe it again to change it
Building
- Builds run one at a time, in a shared line
- Each person can start a limited number of builds per hour
- Repository deploys: public Vite and Create React App projects only, with no server code and no environment variables
Need a back end? See how other builders compare.