Built in Indonesia
for all the sea.
We're a small technical team from Indonesia, the largest archipelago nation on earth. We didn't set out to build a maritime software company. We set out to solve a problem nobody else was taking seriously.
The gap nobody was filling.
Indonesia is the world's largest archipelago, with more than 17,000 islands and over 54,000 kilometers of coastline. Its cargo economy depends on the sea the way other countries depend on highways.
Logistics software has hundreds of solutions for road freight and dozens for air cargo. For sea and maritime operations, especially the small to mid-size operators who move most of the country's goods, the choices were enterprise systems built for global shipping giants, or nothing at all.
Our founder, Unggul Kirindi, saw this gap before most people thought to look for it. The question he kept coming back to was simple:
"There are systems for trucks, and systems for planes. But where is the system for ships? Where is the platform built for the people who actually move cargo across Indonesian waters?"
Unggul Kirindi, FounderAt the time, the honest answer was that it didn't really exist, not in a form a real maritime operator (a fleet manager in Surabaya, a shipping company in Makassar, a freight forwarder in Balikpapan) could actually use and afford.
So we built it.
The sea isn't a transport option here.
It's the only option.
Roads end at coastlines in Indonesia. Rail doesn't cross water, and air freight is expensive and limited by payload. For most inter-island cargo, ships are the only way to move goods, raw materials, and industrial supplies between islands.
For years, the operators running those ships managed the business in spreadsheets, WhatsApp groups, and paper manifests. Quotations were handwritten or built in Excel. Schedules lived in someone's head, and customers had no way to track their cargo except by calling and asking.
Disconnected operations
Finance didn't know a shipment had sailed until the invoice was late. The captain knew the schedule. Nobody else did.
Underserved operators
Enterprise maritime software exists, but it's built for the giants of global shipping, not a ten-vessel operator running routes between Sulawesi and Kalimantan.
Built from the ground up
Not adapted from road freight or ported from air cargo software. Built specifically for how sea cargo operations work in Southeast Asia.
SEALUTION was built to solve Indonesia's maritime complexity first, but the platform underneath isn't limited to Indonesian waters. Ports, currencies, tax rules, and document templates are configurable, not hardcoded to one country. An operator running routes out of Rotterdam or Southampton configures SEALUTION the same way a fleet in Surabaya does. Built here. Not only for here.
We may have gone slightly overboard.
Unggul started by solving the most pressing problems first: scheduling, quotations, basic tracking. But one problem kept leading to another until what we had wasn't a tool anymore. It was a complete operating system for a maritime business.
Vessel registry with document expiry tracking. A route engine that factors in ocean depth, currents, and weather, and gets more accurate with every voyage a fleet actually sails. Fuel consumption profiles per vessel. GPS tracking with fallback for when devices go offline. A full quote-to-invoice financial flow. Bill of lading generation. A customer-facing mobile app, a staff app, and a complete REST API.
Then our first client asked for something we hadn't built yet: a B2B container freight module that didn't follow the standard booking flow at all, because their corporate clients worked completely differently. So we built that too.
We did take that quote as a compliment. In maritime operations, overkill means you won't outgrow the system in six months, and overengineering means the edge cases get handled before they become crises at sea. Operators running fleets on tight schedules with demanding clients don't need software that covers the basics. They need one that handles everything, so they can focus on the part no software can replace: the judgment of an experienced captain on open water.
That's not a marketing line. It's how we built the route engine, and how we think about every feature we add. We give operators better information. We never pretend to replace their expertise.
"Impressive. This is so complete, it's kind of overkill and overengineering, honestly."
The system suggests. The captain decides, always.
Four things we won't compromise on.
Configurable, not generic
Every shipping company runs differently: different ports, routes, rates, document templates, and workflows. SEALUTION configures to your operation. Sea has global standards. Your operation has its own. We're built for both.
Your data stays yours
SEALUTION installs on your own server. Your routes, clients, cargo records, and financial history never pass through our infrastructure. It stays where you control it.
Respect for the operator
Maritime professionals were navigating, scheduling, and managing cargo long before software existed. We don't build systems that try to be smarter than the people using them. We build systems that give them better information, faster.
Built for the long term
We don't sell a subscription and disappear. Every client works directly with the team that built the system: onboarding, training, six months of maintenance, and a real person to call when something matters.
Small team. Full system.
We're a small, focused team from Indonesia, not a large corporation or a venture-funded startup with two hundred engineers. It's a tight group of people who care about getting maritime software right and who have the technical depth to do it properly.
Being small is deliberate. Every client gets direct access to the people who built the system instead of being handed off to a support queue, and when you call, the person who answers usually understands the exact feature you're asking about.
Every title below says "director," and that's deliberate. Nobody here manages a department for the sake of having one. Each director owns a different part of how SEALUTION actually behaves: how the platform is architected and how routes get calculated, how it looks and feels to operate day to day, what "safe" means inside the system's rules, and what the numbers have to prove before anything ships.
We're not directors in the usual sense. We're directors because we direct how this system works.
We're not trying to be a big company. We're trying to be the right one for maritime operators who need software that works the way their business actually works.
See SEALUTION shipping
on your operation.
Tell us about your fleet and routes, and we'll show you the platform configured for your specific operation, in a private demo with the team that built it.