For the group that
actually makes
it past the
planning chat.
TripStream is the platform Bangladesh's Facebook-organised travel groups should have had a decade ago. Co-edit the itinerary in real time. Vote on the food. Collect deposits through bKash and bank transfer, held in Hold.bd escrow. Settle expenses without the spreadsheet. Come home to an album that built itself.
- Live
- tripstream.net
- Services
- 24 Go + 2 Rust
- Maps
- OSM + ORS
- Stack
- NATS, R2, PostGIS
- Day 1, FriDhaka to Sylhet via train, Pansi for dinnerRouted
- Day 2, SatRatargul boat tour, Jaflong, tea estate sunsetVoted
- Day 3, SunSreemangal rainforest, seven-layer teaVoted
- Day 4, MonSylhet to Dhaka, late train, expenses settledAuto album
What is TripStream?
TripStream is a community-first social platform for group travel, built for Bangladesh first. It lets anyone become a tour operator, lets a group co-edit the itinerary in real time, and holds the deposit in escrow until the trip clears the review window.
It is a KaritKarma product, live at tripstream.net. Wenme owns authentication. Darwan enforces RBAC. bKash and bank-transfer collection feed the Payment service. Hold.bd custodies the escrowed deposit until the review window closes. BitsPath carries operator comms. Twenty-four Go production services, two Rust media sidecars, NATS JetStream, and Cloudflare R2 are the TripStream team's own work on that shared spine.
Built for the trips that almost never happened.
Group trips die in the planning chat. TripStream removes the four reasons. The community, the route, the money, the trust.
Travel communities, not Facebook pages.
Tenant equals community. Audiences move from a Facebook timeline into a purpose-built workspace with roles, invitations, member directories, PostGIS-indexed locations, and full-text search over PostgreSQL. Anyone organises, anyone joins, ratings keep both sides honest.
Itineraries co-edited in real time.
Routes drawn through OpenRouteService on OpenStreetMap, polylines stored as PostGIS geography, and single, multiple, or ranked-choice polls to settle food, dates, and the route itself. Itinerary days are executable parent tasks with date-and-time sub-tasks.
bKash and escrow on the deposit.
bKash and bank-transfer collection feed the Payment service. Hold.bd holds the deposit in escrow until the seven-day review window closes, gated on a single event. An append-only double-entry ledger records every movement. Expense splitting with greedy debt simplification at trip end.
Blind-reveal mutual ratings.
Both organiser and travellers rate each other after the trip, but neither side sees the other's score until the seven-day window closes. Five reputation tiers run Newcomer to Legend. Legend requires 25-plus trips and a 4.5-plus average. Trust without gatekeeping, so first-time organisers can climb.
The supply chain for a trip, not just the planning.
Four verticals are live today. Each one is a real product surface wired into the same trip and the same ledger, so the home cook, the stay host, the flight desk, and the trek leader all settle inside TripStream.
Social Kitchen
Home cooks open a kitchen, tell their story, and sell food, with verified-cook hygiene badges and honest ratings. The supply chain for a trip literally starts with who is cooking.
Stays
Supplier rooms, net-rate B2B wholesale, traveler booking, and a supplier inbox. The accommodation vertical the group actually books from.
Flights
Flights, bookings, net-rate, earnings, and operator onboarding. The air vertical wired into the same trip and the same ledger.
Activities
GPX-import MVP for treks, hikes, and cycles, with a leaderboard. Experiences that turn a stay into a trip worth rating.
Money that cannot go missing.
Deposits collected through bKash and bank transfer, held in Hold.bd escrow, released only after the seven-day blind-reveal review window closes, on top of an append-only double-entry ledger.
| Seq | Event | Debit, credit | BDT |
|---|---|---|---|
| 0181 | Deposit.Collected bKash, traveller 04 | traveller-04 escrow:holdbd | 1,500.00 |
| 0182 | Deposit.Collected bank transfer, traveller 05 | traveller-05 escrow:holdbd | 1,500.00 |
| 0214 | Expense.Recorded boat hire, Ratargul, split 10 | trip:expenses organiser:float | 3,200.00 |
| 0241 | ReviewWindow.Closed T+7d, blind reveal | escrow:holdbd organiser:payout | 15,000.00 |
| 0242 | Settlement.Simplified 9 balances netted to 3 transfers | traveller-07 traveller-02 | 640.00 |
Hold.bd escrow on the deposit
Rail 01The trip deposit sits in Hold.bd escrow while planning happens. Release to the organiser is gated on one event only: the close of the post-trip review window. No deposits vanishing with a missing organiser.
7-day blind-reveal reviews
Rail 02Organiser and travellers rate each other after the trip, and neither side sees the other's score until the seven-day window closes. No retaliation ratings, no score-trading, and a background closer fires the escrow release on the same clock.
Append-only double-entry ledger
Rail 03Every payment event writes a debit and credit pair into the Payment service ledger. Entries are never edited and never deleted, so the trip's money has a complete, replayable history from first deposit to final settlement.
Greedy debt simplification
Rail 04At settlement the platform matches the largest debtor with the largest creditor and repeats until the graph clears, so a group of ten settles the whole trip in the fewest possible transfers instead of a web of IOUs.
Five surfaces a travel group actually uses.
Not a feature dump. Five daily-use surfaces, each behind Darwan RBAC enforced per route across the 24-service Go backend.
Trip discovery feed
01Browse open trips by destination, dates, budget, and group size. Full-text search over PostgreSQL, geo via PostGIS, and materialised views ranking popular destinations.
Expense splitting
02Per-trip ledger inside the Payment service. Add an expense, tag who shared it, watch the platform resolve everyone to a minimal-transfer settlement using greedy debt simplification.
AI trip assistant
03Groq completions on llama-3.3-70b-versatile. Ask for a three-day Sylhet plan for ten people under 12,000 BDT and get a costed draft to vote on, inside the same workspace as the itinerary.
Auto photo albums
04EXIF extraction, WebP thumbnails, and an album assembled automatically the moment the trip completes. The memory engine that brings the group back to plan the next one.
Operator storefronts
05Custom domains with a theme system and a byte-stable public resolver. A traveler grows into an operator with a branded storefront, packages, bookings, and a back office.
From idea to album, in four steps.
The lifecycle the Trip service actually runs. Seven internal states, four visible steps for the human in the group.
- 01
Find a community or start one
Join a travel community, or spin one up for your university group, photography circle, or weekend friends. PostGIS-tagged location, public or invite-only, with roles and invitations built in.
- 02
Propose a trip, or join an open one
Pick dates, a destination, a budget band, a group ceiling. The trip moves through a seven-state lifecycle, draft to open to booking to active to completed to archived or cancelled.
- 03
Plan it together in real time
Co-edit the itinerary, vote on the food stops with ranked choice, draft the route through OpenRouteService, let the AI assistant cost the day. Group chat in the same workspace, no separate scrollback.
- 04
Pay, travel, remember
Deposit through bKash or bank transfer, held in Hold.bd escrow. On the trip, expense splitting tracks the group's cash. After the trip, GPS-grouped photo albums close the loop.
TripStream vs Wanderlog vs TripIt vs the WhatsApp group.
Wanderlog is the closest western analogue, built around the itinerary rather than the group's money. TripIt aggregates a solo business traveller's bookings. The WhatsApp group is where most Bangladeshi trips start, and stall.
| Capability | TripStream | Wanderlog | TripIt | |
|---|---|---|---|---|
| Real-time itinerary co-editing | Async edits | |||
| Group voting on route, food, dates | Ranked choice | Comments only | Reactions | |
| bKash and bank transfer collection | ||||
| Deposit held in escrow | Hold.bd | |||
| Expense splitting with debt simplification | Manual | |||
| Mutual blind-reveal ratings | ||||
| Home-cook, stays, flights, activities verticals | 4 verticals, live | |||
| Operator storefront on a custom domain | ||||
| Open-source maps, no Google lock-in | OSM + ORS | |||
| Installable PWA, no app store |
Scroll for full table
One product, three surfaces, live today.
The KaritKarma subdomain pattern, shipped. Each audience gets the surface built for it, on its own subdomain, sharing one member and one ledger.
Travelers plan, chat, pay, and photograph the trip in their pocket.
Tour operators run storefronts, bookings, CRM, manifest, and profitability.
The KaritKarma-side control plane for cross-tenant provisioning and monitoring.
Standing on the same shared spine as the rest of KaritKarma.
Wenme for auth. Darwan for access control. Hold.bd for escrow. BitsPath for operator comms. The 24 Go services, the two Rust sidecars, and the four live verticals are the TripStream team's own work on that spine.
What people ask before they book.
Each answer mirrors the FAQPage structured data on this page, so AI answer engines and audit reviewers see the same wording.
- 01What is TripStream?
- TripStream is a community-first social platform for group travel in Bangladesh, built by KaritKarma. It bundles travel communities, real-time itinerary co-editing, group voting, bKash and bank-transfer collection with Hold.bd escrow on the deposit, expense splitting, mutual blind-reveal ratings, an AI trip assistant powered by Groq, and auto photo albums. Twenty-four Go production services run with two Rust media sidecars, on NATS JetStream and Cloudflare R2, behind a three-tier subdomain pattern. It is live at tripstream.net.
- 02How is TripStream different from a WhatsApp group, Wanderlog, or TripIt?
- A WhatsApp group has no purpose-built planning tools, so the route, the money, and the decisions drown in the scrollback. Wanderlog and TripIt centre on the itinerary for an individual traveller. TripStream is built around the group: real-time co-editing, single, multiple, and ranked-choice polls, bKash and bank-transfer collection with Hold.bd escrow on the deposit, blind-reveal mutual ratings, and auto photo albums that bring the group back for the next trip.
- 03What runs under the hood?
- Twenty-four Go microservices on a 21-package shared kernel, two Rust sidecars (safety-scanner, an ONNX NSFW classifier, and scene-tagger, a Places365 ResNet18 model), NATS JetStream with Limits retention as the production event backbone, PostgreSQL 18 with PostGIS, Redis 8.8, and Cloudflare R2 for object storage. The frontend is Next.js 16 with React Compiler and a Serwist PWA. Maps run through Leaflet on OpenStreetMap, with an OSM give-back. Twenty-nine containers ship in docker-compose.prod.yml.
- 04Can TripStream actually split expenses for a group?
- Yes. Every trip has a Payment-service ledger that records expenses against contributors. At settlement the platform runs greedy debt simplification, matching the largest debtor with the largest creditor until the graph clears, so a group of ten settles with the fewest possible transfers. The same ledger sits next to bKash and bank-transfer collection, so the trip runs cashless end to end.
- 05How does TripStream protect the trip deposit?
- Deposits are collected through bKash and bank transfer and held in Hold.bd escrow. Release to the organiser is gated on a single event: the close of the seven-day post-trip review window. Underneath, the Payment service keeps an append-only double-entry ledger, so every taka is recorded as a debit and credit pair that nothing can silently edit. At settlement, greedy debt simplification nets the group's balances into the fewest possible transfers.
- 06Is TripStream just travel, or does it cover the supply side too?
- Both. Four verticals are live today: Social Kitchen (home cooks selling food with verified hygiene badges), Stays (supplier rooms and net-rate B2B wholesale), Flights (bookings, net-rate, earnings), and Activities (GPX-import treks and hikes with a leaderboard). Any traveler can grow into an operator with a branded storefront on a custom domain, a back office with CRM, manifest and roster, and a per-trip cost sheet with a profitability report.
The group trip that
actually happens.
Plan together, pay into escrow, travel, and let the album build itself. Live at tripstream.net with four verticals shipping today.