SaturnusGo ~ on the waitlist
Status: Pre-launch
About the Founder

From Buenos Aires streets to a new class of travel superapp

Why me, why now — and why SaturnusGo isn’t a clone but a new category product.

I moved to Argentina to start from zero — and ran head-first into a broken experience: one app for rides, another for hotels, another for events, another just to save places. Payments fail, cards don’t go through, “premium” adds nothing. Five apps for a single evening.

My first instinct was “I’ll build a local taxi app.” But the world doesn’t need another clone. The real pain is fragmentation and the absence of trust. People need one continuous flow — rides, bookings, places, tickets and wallet working together from the first tap.

  • Built SaturnusGo solo for 2+ years.
  • 12–16 hours a day; hundreds of design/code iterations.
  • Pixel-level UX judgement; clear receipts over “wow effects”.
  • Financial layer that works across borders and edge cases.
  • Production-grade modular architecture (not a demo).
  • Obsession with trust, predictability, honest interactions.
“Every founder knows the nights when nothing works and the days when no one cares.
That’s when you either quit — or keep going. SaturnusGo is what happens when you don’t quit.”
— Mercury, Founder of SaturnusGo
Founder’s Story

Clones are easy. Building a coherent ecosystem is hard.

The pivot from “another taxi app” to a new category product.

Start and reality

I began with a local taxi idea. It became obvious fast: the problem isn’t the “order ride” button; it’s the gaps between services. Route → ride → check-in → events → payment → receipts — this must be one motion, with no context switching or “will the card fail again?” anxiety.

Reframing

That’s how SaturnusGo emerged as an ecosystem: rides, places & collections, hotels, events, wallet, loyalty — in one UX. With a financial backbone that behaves consistently across countries.

The founder’s path

It was hard — regularly. Days when nothing works, nights when everything breaks. I kept moving: rewriting modules until they “clicked”, polishing micro-interactions so the interface feels honest and resilient. When depression hit, I treated it like a product problem — reduce chaos, regain control, step by step.

That’s how my principles formed: earn trust first, hide complexity inside the system, keep the outside simple and predictable.

What’s built

What is actually done

Not a demo video — a live product stack.

  • One continuous user flow

    Doorstep → ride → bookings → events → wallet — no gaps or payment surprises.

  • Financial backbone

    Local rails in LATAM/MENA, transparent receipts, bonuses/subscriptions, tokenized cards.

  • Trust by default

    Verified partners & drivers, privacy by default, predictable UX patterns.

  • Engineering foundation

    Modular architecture, offline-resilient flows, tight perf & animation budgets.

Where we are now

The ecosystem is almost ready

What separates SaturnusGo from the world: the driver app and launch resources.

What remains

  • Finish the production-ready driver app.
  • Operational scaffolding to enter the first cities.
  • Hire the core team across product, infra and ops.

What I’m looking for

  • Partners and investors who share the vision.
  • Local synergies: LATAM → UAE → Europe → Rest of the world.
  • Resources for the launch and early scale-up.
Operating principles

How I make decisions as a founder

Simple rules I follow every day.

Trust → Metric #1

The best UX is the one people trust. Clear receipts beat fireworks.

One motion

Users shouldn’t think in “apps”. One coherent scenario from point A to life.

Complexity inside

Hide complexity in architecture; keep the outside simple and predictable.

Let’s talk

Ready to bring SaturnusGo to the world

If this resonates, I’ll show the live build and discuss the launch.