Your page, your flows, one address
An app is a website hosted next to the automation it needs: the event page’s RSVP form runs the flow that saves the answer and e-mails you, all in one project.
A form that runs a flow
Publish the flow, turn on its endpoint, and the page calls it in one line through the helper every app address serves. The answer is the flow’s output.
Learn more →<form id="rsvp">
<input name="name" placeholder="Your name" required>
<select name="guests"><option>1</option><option>2</option></select>
<button>Confirm attendance</button>
</form>
<script src="/_waiso.js"></script>
<script>
rsvp.onsubmit = async (e) => {
e.preventDefault()
const f = new FormData(rsvp)
await waiso.call('rsvp', { name: f.get('name'), guests: Number(f.get('guests')) })
rsvp.outerHTML = '<p>See you there!</p>'
}
</script>The work behind it is code you own
Each step is a script in Python, TypeScript or another supported language — save to a sheet, check a list, send an e-mail — with every run on record.
Learn more →def main(name: str, guests: int = 1):
# A step of the "rsvp" flow: save the answer, then the next step e-mails the couple.
sheet.append_row([name, guests])
return {"saved": True}Logins, versions and your domain
A flow of yours decides who signs in, and endpoints receive who the visitor is. Every publish is a version you restore in one click; paid plans add your own domain.
Learn more →Questions
Do I need to know how to build websites?
No. Ask the project assistant for the page you want and it writes the files; or upload a site made in any other tool.
Can I take the site somewhere else later?
Yes. Download it as a zip and host it anywhere: it keeps calling the same endpoints.
Is there a free plan?
Yes: one app with 50 MB on the Free plan, with a small “Made with Waiso” strip. Paid plans add more apps, space and your own domain.
Can one app read another app’s data?
No. Each app has its own address on a domain separate from Waiso, so storage, cookies and pages stay apart.