Product families
One company.
A full basket of digital systems.
These are not separate businesses. They are FruitStack product families, built on one interface language and one set of data conventions. Start with one product, or combine several into a connected system built around your operation.
Product architecture
Four groups. Eleven products.
Grouped by what they do rather than by which department bought them. Most organizations start in one group and reach into a second within the first year.
Book, move, and transact
Everything that touches a customer, a payment, or a departure time.
Manage people and operations
The internal side: who is working, what is open, and who signed off.
Understand places and public information
Records and geography, made searchable and defensible.
Connect and present
The plumbing underneath and the surface the public sees.
Together
Products that already know about each other.
Because they share one data model, combining products removes work rather than adding an integration project. A few of the pairings that come up most often:
- Lime Book + Coconut Move A guest books an activity and the pickup is already assigned.
- Lime Book + Passionfruit Events Event tickets and everyday reservations share one capacity ceiling.
- Guava Rent + Tamarind Connect Rental contracts and deposits reconcile against accounting on their own.
- Papaya People + Breadfruit Ops The schedule knows who is certified for the work order.
- Soursop Public + Starfruit Map A public record search returns the parcel it belongs to.
- Pineapple Commerce + Mango Experience The storefront and the brand behind it are built as one thing.
In detail
Every product, and what it actually covers.
Lime Book™
Bookings, availability, payments, confirmations, waivers, and customer accounts.
Everything that has to happen between someone wanting a spot and someone standing at your counter: live availability, capacity rules that change by season, deposits and balances, digital waivers signed before arrival, and a check-in screen your staff can actually use with one hand.
Coconut Move™
Dispatch, routes, drivers, vehicles, passenger manifests, flight tracking, and notifications.
Built for operators moving people between docks, terminals, and properties. Assign vehicles and drivers, hold a manifest that matches what the captain has, watch inbound flights so pickups shift before the phone rings, and send passengers the message they need without anyone typing it.
Guava Rent™
Availability, contracts, deposits, inspections, damage records, maintenance, and payments.
Rental operations where the paperwork is the risk. Digital agreements signed on a phone, photo inspections at pickup and return, damage tied to a specific rental rather than a memory, deposit status everyone can see, and maintenance intervals that pull a unit off the calendar automatically.
Papaya People™
Employee onboarding, records, leave requests, scheduling, training, evaluations, and internal documents.
Staff records that stop living in a filing cabinet and three spreadsheets. Onboarding checklists that finish, schedules published to the people working them, leave requests with an approval trail, certification expiry that warns you before it lapses, and evaluations on a real calendar.
Breadfruit Ops™
Tasks, approvals, work orders, documents, dashboards, reporting, and departmental workflows.
The internal spine. Work orders raised, routed, and closed with evidence attached. Approvals that show who is holding the queue. Documents filed against the thing they belong to. Reports that leave on a schedule instead of being rebuilt by hand every month.
Soursop Public™
Searchable records, public dashboards, project trackers, historical archives, and source-linked information systems.
Public information that holds up to scrutiny. Searchable records with the source document one click away, project trackers that show status and the date it changed, archives that stay stable at the same URL, and a visible correction history rather than a quiet edit.
Starfruit Map™
GIS tools, parcel systems, asset maps, address crosswalks, service territories, and location intelligence.
Mapping wired to the records behind it. Parcel and zoning layers, infrastructure and asset positions, service territory boundaries, and address crosswalks that reconcile territory addressing with the mainland formats your other systems insist on. Filter on the map, export the result.
Passionfruit Events™
Ticketing, vendors, credentials, schedules, sponsors, guest lists, and event operations.
Events where the operation is the hard part, not the poster. Ticket tiers and scan-in, vendor assignments and load-in windows, credentials printed against a list that is actually current, sponsor deliverables tracked to delivery, and guest check-in that works when the signal drops.
Pineapple Commerce™
Online ordering, customer accounts, payments, subscriptions, loyalty, delivery, and inventory.
Selling online without handing your margin to a platform. Ordering tied to real stock counts, local payment processing, customer accounts and repeat orders, subscription and loyalty balances, and a delivery queue your drivers can work from directly.
Tamarind Connect™
Data cleanup, database integrations, APIs, payment systems, calendars, accounting tools, and automation.
The layer that makes the rest of it stop being manual. Cleaning up the data you already have, connecting the systems you are keeping, moving records between them on a schedule, and showing you plainly which records failed and why instead of silently dropping them.
Mango Experience™
Branding, websites, content, photography, interface design, and customer-facing digital experiences.
The customer-facing surface of the stack, not a separate agency. The booking page people actually land on, the confirmation email they read, the photography and copy carrying the brand, and the interface language shared across every FruitStack product you run.
Start here
Not sure which products you need?
Most people are not, and that is fine. Describe the operation and we will tell you which parts of the stack apply, which ones do not, and what a sensible first phase looks like.
How every engagement runs