Jettova Is Officially Jettova, Inc. — and Here's What Made It Inevitable

Jettova started as a side project — a way to turn a vague travel idea into a real itinerary without spending a Saturday cross-referencing Reddit, Skyscanner, Booking.com, and a half-finished spreadsheet. As of this month, it's not a side project anymore. Jettova is officially incorporated as Jettova, Inc., a US C-corporation registered in June 2026. The product is the same product. What changed is the structure behind it, and the way that structure changes what we can build next.

**Why incorporate now and not earlier.** Incorporation isn't free — it adds tax filings, registered-agent costs, legal-entity bookkeeping, and a layer of formality that's actively in the way of the early experimentation that makes a small product good. The right time to incorporate is when the product stops being an experiment, when there are real users with real expectations, real money flowing through partner channels, and real liability questions in the room. Jettova hit all four in the same month. Native iOS shipped, native Android followed two weeks later, the partner-attribution pipeline started crediting referrals through to confirmed bookings, and the in-app activity ledger finally had enough signal that we could ship the per-partner roster page without it reading as zeros.

**What it means practically for users.** Nothing breaks. No data moves. No accounts get migrated. The product on the homepage, in the iOS app, and in the Android app is the same product it was last week. What changes downstream is the legal substrate: the entity that holds the customer relationship, the entity that signs partner contracts, the entity that issues IRS forms to anyone who earns referral commission through us. The mailing address on the footer (1178 Broadway, 3rd Floor #4609, New York, NY 10001) is the entity's registered address. Email senders now show 'Jettova, Inc.' in the address block. Schema.org Organization markup picks up the legal name and the founding date so search engines tie the brand to the corporation correctly.

**The two apps that ran in parallel.** Most of the technical work that justified incorporation happened in the apps, not on the web. The web version had been the entire product since launch — a single Next.js codebase with a planning funnel, results page, saved trips, and a referral pipeline. Mobile users got a responsive web view. That worked until it didn't: push notifications were impossible without a PWA workaround that broke on iOS Safari, share-trip URLs didn't deep-link into native back-stacks, and the group-planning rooms (which are inherently social — invite, vote, settle up) felt anemic without a notification surface. Two native apps fixed all three at once.

**iOS first, then Android — five tabs each.** Both apps ship the same five tabs in the same order: Plan, Rooms, Discover, Trips, From Video. The Plan tab is the multi-step funnel (Vibes → Destination → Budget → Storyboard → Review), same SSE-streamed trip generation as the web. Rooms is the group-planning surface — invite friends by link, everyone votes on destinations + dates, a 7-day itinerary builds when consensus lands, the receipt-scanner + settle-up math runs after the trip. Discover is community trips you can clone and modify. Trips is your saved itineraries. From Video is the import-a-TikTok-or-YouTube flow that ships a 7-day itinerary in 10 seconds. iOS uses native SwiftUI, Android uses Jetpack Compose; the API surface they hit is the same Vercel-hosted Next.js backend the web uses, so feature parity is mostly a UI port problem, not a backend duplication problem.

**What native unlocks that web couldn't.** Push notifications for room state changes (a friend joined, consensus reached, settle-up balances updated). Share Sheet entries on iOS, intent filters on Android, so a TikTok URL can be shared directly into Jettova without copy-paste. Lifecycle-tied background fetch so a trip with departure tomorrow surfaces a check-in nudge. Stable per-device identity for the room-voting flow (which used to rely on cookies that browsers periodically nuked). Universal links / Android App Links so a `jettova.com/room/ABCD` URL opens the room dashboard inside the installed app, not a Safari tab.

**The partner page finally has signal.** A subtle but load-bearing fix shipped alongside the apps: server-side user-id resolution in the analytics ingest. Before it, every signed-in user's events still landed in the events table with user_id = null because the client never bothered to populate the field on the way out. Auth DAU on the admin dashboard read zero. Auth rate on the cohort view read 0% of 949 anonymous events. The fix — resolving user_id from the Supabase auth cookie inside /api/track itself, regardless of what the client sent — lit up every downstream surface that depended on that join. Partner detail pages now show per-attributed-user in-app activity (events fired, sessions, last seen, deepest funnel stage reached, whether they actually clicked through to book). That visibility is the thing that lets us write partner contracts with confidence in the conversion math, which is the thing that lets us scale partner outreach, which is the thing that justifies the legal entity in the first place.

**What's next.** Incorporation isn't a feature; it's a foundation. The list of things it unblocks is mostly invisible to users — formal partnership agreements with new affiliate networks, the ability to raise from US investors who don't write checks to unincorporated entities, formal terms of service that name a defendant (which sounds grim but is what every business-to-business relationship requires), commercial general liability insurance. The visible things — sign-up incentives, group-discount partnerships with travel insurance providers, a paid 'concierge' tier for high-budget trips, a referral program with cash-out support — are downstream of having a corporate entity that can hold contracts and money. We'll ship them in that order over the back half of 2026.

**The honest reflection.** The product is more or less the same product it was three months ago. What's different is that the surface area now spans web + iOS + Android, the analytics actually attribute users to the partners who brought them, the legal substrate exists to sign contracts and accept investment, and the team has enough confidence in the numbers to commit to the next 12 months of roadmap without hedging. If you're a user, you don't need to do anything — the product just keeps working, on more devices, with better notifications, with more accurate referral credit, and with a real company behind it. If you're a partner or an investor or just someone who's been watching: this is the moment things get serious.