Self-host PiggyBack
Same app, same features, zero subscription. Run it on your own Supabase + Vercel. The whole stack, including this landing page, ships in the repo.
Four steps. About 15 minutes.
Fork the repo
Click Fork on GitHub, or clone locally with `git clone`.
Create a Supabase project
Free tier works fine. Run the migrations in supabase/migrations/ via the SQL editor or the Supabase CLI.
Deploy to Vercel
Click Deploy on Vercel and link your fork. Set the env vars from .env.local.example. Vercel's hobby plan is enough.
Connect Up Bank
In settings, paste your Up PAT (generate one at api.up.com.au). Optionally enable the webhook for real-time syncing.
Why self-host?
Because Up Bank's API doesn't allow us to hold your credentials
Australian banking regulations and Up Bank's API terms don't permit a third party to store and serve your banking data back to you. PiggyBack is architecturally a SaaS that can't be a SaaS. So we made the architecture a feature: you run the app yourself, and we offer to manage the boring bits for you (A$19/month) if you'd rather not click around Vercel and Supabase yourself.
- Your bank credentials live in your encrypted Supabase row
- Your transactions live in your Supabase database
- Runs on your Vercel account (free tier works for years)
- MIT licensed. Fork it, change it, make it yours.
- No middleman between you and your bank
You own the whole stack
Same code, same features, zero lock-in.
Don't want to manage Vercel and Supabase yourself?
Try the managed tier — A$19/month