For pre-PMF, pre-first-hire SaaS founders
E2E + Visual Testing for SaaS MVPs.
Your MVP deserves real tests. Without a real QA team.
You shipped v1 alone. There's no QA team, no on-call rotation, no design partner clicking through every release. Every push is a prayer. Users find bugs in features you haven't touched in weeks. Lastest gives pre-PMF founders real E2E + visual tests in 5 minutes - without hiring anyone.
Why Not Just Click Through It Yourself?
You don't have a QA team. That doesn't mean you don't need tests.
Pre-PMF, you're iterating on the product every day. Every release ships with three things you didn't mean to ship. The classic answer is “we'll add tests after PMF” - and the classic outcome is that the user who finds the broken signup flow churns before you ever talk to them. Two ways to handle this.
“We'll add tests after PMF.”
Every release is a prayer. You click through signup once, push, and hope. A user emails you a screenshot two weeks later: pricing page is broken on Safari. You haven't touched that page in a month. You don't know which commit did it. You spend an afternoon bisecting instead of building.
- Bugs surface from users, not from CI
- You bisect manually - no diff history, no screenshots
- Pre-PMF churn is silent - they don't email, they leave
- Hiring a QA contractor burns runway you don't have
Use Lastest. Record once. Replay forever.
Click through the three flows that matter - signup, paywall, core feature - once. Lastest captures them as deterministic Playwright with a visual baseline. Every push replays the full suite, zero AI calls, zero maintenance, zero SaaS bill. The day you ship a regression, you know before the user does.
- 5-minute setup - docker-compose up, record, done
- $0 forever - self-host or use the free tier
- Visual diffs catch what the DOM hides - 3 diff engines
- Self-healing selectors - survives weekly redesigns
- Bring your own AI - Claude, OpenAI, OpenRouter, local Ollama
Built for Pre-PMF Iteration
Iterate fast. Without breaking the basics.
Two features that matter when you're shipping a v1 alone, every week.
01 · Record
Click signup → paywall → core feature. That's the test.
Open the recorder, walk through your three critical flows, hit stop. Lastest generates deterministic Playwright code with 7-layer fallback selectors. No selectors to maintain, no docs to read, no weekend gone. You go back to shipping features, not tests.
- Captures uploads, downloads, clipboard, network calls
- Works with Stripe test mode, magic-link auth, OAuth
- Multi-step screenshots so you see what happened, step by step
02 · Visual diff
Did the last refactor break a page you haven't touched in weeks?
Pre-PMF refactors are constant. You move a component, rename a prop, bump a dependency, and three pages quietly look wrong. DOM tests pass. Lastest compares screenshots with three diff engines (pixelmatch, SSIM, Butteraugli) so silent visual regressions show up keyed to the commit that caused them.
- Auto-mask timestamps, UUIDs, and rotating content
- Branch-to-branch compare for pre-deploy review
- One-click approve/reject - you're the only reviewer anyway
Common questions for SaaS MVPs
- When is the right time to add E2E tests to a SaaS MVP?
- The week your first paying user signs up. Before that, you are the only stakeholder. After, every regression is a refund or churn. Lastest gives MVPs deterministic E2E and visual coverage in 5 minutes. Record signup, paywall, and core feature once, then replay on every push. No QA hire required, $0 self-hosted.
- How do I test a pre-PMF MVP that changes every week?
- Cover only what cannot break: signup, paywall, the one core action your retention depends on. Re-record when those flows change intentionally; visual diffs catch every unintentional change. Lastest stores the suite as Playwright code keyed to git SHA so you always know which commit broke what.
- Can I use Lastest before I hire my first engineer or QA?
- Yes. Lastest is built for solo founders running pre-PMF SaaS. No QA expertise, no Playwright experience, no test DSL to learn. Click through the flow, hit stop, ship. The hosted free tier at app.lastest.cloud means you do not even need to run Docker until you scale.
- My MVP is on Stripe and Supabase. Does Lastest work with those?
- Yes. Use Stripe test mode (card 4242 4242 4242 4242) for checkout flows, and either record Supabase auth as a UI flow or use a Playwright setup file that hits the Supabase REST API once and reuses the session. Walkthroughs live at /for/stripe-apps and /for/supabase-apps.
- Will tests slow me down when I am still iterating fast?
- No, because you only test what matters: the three flows that lose money if they break. Recording a test takes 30 seconds; the rest of your iteration speed is untouched. Self-healing selectors mean refactors usually pass without re-recording, and visual diffs surface the silent regressions JSDOM unit tests miss.
- How much does this cost while I am bootstrapping?
- Self-hosted Lastest costs $0 (FSL-1.1-ALv2 license), runs on a $5 VPS via Docker Compose, with no per-screenshot fees and no seat limits. AI is only used during test creation; replays in CI are pure Playwright with zero token cost. Most pre-PMF MVPs run the entire setup inside the GitHub Actions free tier.
- How do I avoid flaky tests when my MVP UI changes weekly?
- Lastest uses 7-layer self-healing selectors (data-testid → id → role → aria → text → CSS → OCR), auto-waits for network quiescence, and AI-triages every failure as real regression vs flake vs env issue. When a Tailwind refactor lands, the suite stays green; when an actual regression ships, you see the pixel diff, not a flake stack trace.
Real tests for your MVP
in five minutes.
No QA hire. No procurement. No SaaS bill. No per-screenshot fees. Open source, FSL-1.1-ALv2 licensed, $0 forever. Runs on your laptop or a $5 VPS.
★ Star & Install from GitHub →# 1. clone
$ git clone https://github.com/las-team/lastest
# 2. start
$ cd lastest && docker-compose up -d
# 3. record your first MVP test
$ open http://localhost:3000
✓ ship pre-PMF, sleep post-deploy.