Booking and scheduling
Reservation platforms for beaches, tours, activities, appointments, facilities, and events.
- Availability and capacity
- Payments and receipts
- Waivers and check-in
St. Thomas · U.S. Virgin Islands
The Caribbean runs differently.
Its software should too.
FruitStack designs custom booking platforms, dispatch systems, civic-data tools, GIS products, internal portals, and operational software for organizations across the U.S. Virgin Islands and the wider Caribbean.
Designed, deployed, and supported from St. Thomas.
Console
Today
Bookings
Dispatch
Capacity
Payments
Reports
Bookings today
42
Spaces left
8
Vehicles active
3
Beach capacity 42 / 50
ReservedWalk-upAvailable
Next departures
RT
Red Hook → Cruz Bay
Vehicle 04 · 26 passengers
10:30 AM
CB
Crown Bay pickup
Vehicle 02 · 8 passengers
Holding
MB
Magens Bay shuttle
Vehicle 07 · 14 passengers
Boarding
Why FruitStack
Software built for the way islands actually operate.
Most software asks you to change your operation to fit the system. FruitStack does the opposite. We design and build software around your team, your customers, and the way work already gets done.
From bookings, payments, online ordering, and dispatch to internal portals, public records, GIS tools, and executive dashboards, every platform is tailored to the problem it needs to solve.
And because we build for the Caribbean, local realities are never treated like edge cases. Ferry schedules change. Addresses do not always follow mainland formats. Internet connections drop. Storms disrupt operations. Your software should be ready for all of it.
The stack
One company. A full basket of digital systems.
FruitStack products are modular. Start with one, or combine several into a connected system built around your operation. Six of eleven shown here.
Lime Book™
Bookings, availability, payments, confirmations, waivers, and customer accounts.
Coconut Move™
Dispatch, routes, drivers, vehicles, passenger manifests, flight tracking, and notifications.
Starfruit Map™
GIS tools, parcel systems, asset maps, address crosswalks, service territories, and location intelligence.
Breadfruit Ops™
Tasks, approvals, work orders, documents, dashboards, reporting, and departmental workflows.
Soursop Public™
Searchable records, public dashboards, project trackers, historical archives, and source-linked information systems.
Papaya People™
Employee onboarding, records, leave requests, scheduling, training, evaluations, and internal documents.
What we build
Systems, not websites with a form attached.
Six areas cover most of what organizations here ask us for. Most engagements end up touching two or three of them.
Transportation and rentals
Reservation, rental, and dispatch tools for taxis, ferries, charters, fleets, equipment, and vehicles.
- Dispatch and assignment
- Fleet and inventory
- Rates and seasonal rules
Portals and internal systems
Secure portals that give employees, customers, vendors, and leadership the information they need.
- Role-based access
- Document handling
- Approval workflows
Government technology
Public information systems, civic-data platforms, case tools, and internal government workflows.
- Public-facing records
- Internal case tools
- Reporting and exports
GIS and property intelligence
Interactive mapping connected to parcels, infrastructure, property information, and operational data.
- Parcel and zoning layers
- Infrastructure overlays
- Search and filtering
Integrations and reporting
Custom databases, system integrations, scheduled reports, and workflow automation.
- System integrations
- Scheduled reporting
- Workflow automation
How FruitStack works
Built here. Supported here. Designed around the real operation.
18.34° N
Practical scope
We build the system the operation actually needs, not the version that looks impressive in a demo. Scope that survives the first busy week is worth more than scope that photographs well.
64.93° W
Standard hosting
Reliable, portable hosting without unusual infrastructure or platform lock-in. If you ever want to move the system somewhere else, nothing about how it was built should stop you.
ALT 0 M
You own it
The client owns the code, the accounts, the data, the documentation, and the operational knowledge. Ownership is written into the engagement, not offered as a favour later.
BEARING 090
Local context
Territory addressing, local payment processors, ferry schedules, hurricane season, and multi-island logistics are part of the design conversation from the first meeting, not discovered during testing.
One system
One system. A clearer operation.
Bring bookings, capacity, payments, routes, customer records, documents, reporting, and staff workflows into one system designed around the organization.
Modules
Overview
Reservations
Fleet
Customers
Documents
Staff
Search reservations, vehicles, customers, documents
Today
This week
Unassigned
Needs approval
Confirmed
126
Assigned
118
Open
8
Queue
04
Charter transfer — party of 6
Awaiting vehicle assignment
Open
11
Equipment rental return
Inspection photos attached
Closed
27
Vendor invoice
Needs department approval
Review
Field view
Vehicle 04
Next stop
Red Hook dock
26 passengers
Boarding
Manifest26 / 30
Checked in
✓
Party of 4Waiver signed
✓
Party of 2Paid at booking
ReservationConfirmed
VehicleAssigned
ReportGenerated
PaymentMatched
CapacityUpdated
DocumentApproved
Who we build for
Built for organizations that keep the islands moving.
The operational problems repeat across sectors. The systems that solve them do not, which is why we do not sell one.
Hospitality and resorts
Front desk, activities, and amenities each keep their own list.
Unified guest reservations
Tourism and activities
Capacity is guessed at, and no-shows are absorbed rather than measured.
Timed booking with capacity
Transportation and marine
Dispatch runs on phone calls and a whiteboard.
Dispatch and manifests
Government and public agencies
Records exist but the public cannot find them.
Searchable public records
What you can expect
No client logos on this page.
Much of what we build runs inside an organization and is not ours to display. Rather than borrow credibility with numbers nobody can check, here is what the engagement actually gives you.
- Built around the operation, not fitted to a generic platform
- Designed for the bandwidth and connectivity that actually exists here
- Clear scope, clear ownership, and written documentation
- Direct access to the people building the system
- Maintenance that continues after launch
- Designed to connect with the tools you are keeping
Where we work
Across the territory, from St. Thomas.
Same time zone, same conditions, and no need to explain how anything here works before we start.
St. Thomas
Cruise arrivals, charter and taxi operators, retail in Charlotte Amalie and Red Hook, and restaurants working two very different seasons. Most of our work starts here.
St. John
Villas, day charters, and small operators where almost every booking begins with a search from off-island, weeks before anyone lands.
St. Croix
A larger local economy and a smaller share of visitor traffic, so the balance between serving residents and serving arrivals sits differently.
We also work with organizations in the British Virgin Islands and across the wider Caribbean, where multi-island logistics, local payment processing, variable bandwidth, and storm season shape the work in much the same way.
Start here
Tell us what the operation needs to do.
Show us the spreadsheets, the bottlenecks, the disconnected systems, and the manual processes. We will map the solution and explain what it takes to build.
How every engagement runs
Understand
We watch the current process before anything is designed.
Map
Scope, phases, and what is out of scope, agreed in writing.
Build
In phases you can see, not one long silence.
Launch
Documentation and account ownership handed over with it.
Support
Continuing, with the same people who built it.