Why We Built for
Indonesia First.

When you set out to build software, you get to choose your first customer. Most companies choose the easy one. A single city, a simple supply chain, a market that already has three competitors proving the idea works. We chose the hardest market we could find, and we did it on purpose.

A country made of water

Indonesia is the largest archipelago on earth. More than 17,000 islands, spread across a coastline longer than the distance from London to Los Angeles and back. For most of the country, the sea is not a transport option among several. It is the only option. Roads stop at the coastline. Rail does not cross open water. Air cargo is fast but expensive and limited by weight.

That means moving goods between islands has always depended on ships, and on the people who run them. Small operators, family businesses, regional carriers who know their routes better than any outsider ever could. They move raw materials, food, fuel, and everyday goods for a country of more than 270 million people.

Hard is not the same as bad

Here is the part people usually get backwards. Building for a hard market is not a handicap. It is a filter. If a platform can handle Indonesia's sea logistics, with its scattered ports, unpredictable weather, and thousands of small routes that do not follow a straight line, it can likely handle a calmer market with room to spare.

The opposite is rarely true. Software built for a simple, single route market tends to fall apart the moment real complexity shows up. We would rather earn our stripes where the conditions are toughest, then carry that strength everywhere else.

Roads end at coastlines here. Rail does not cross water. For most inter-island cargo, ships are the only way to move goods between islands, and the operators running them deserved better tools than a spreadsheet and a phone.

The gap nobody was closing

Enterprise maritime software already existed before we started. It was built for the giants of global shipping, container lines with fleets in the hundreds and IT departments to match. It was never built for a ten vessel operator running routes between two provinces, and it was priced like it never expected to serve one.

So the operators who actually move most of Indonesia's cargo kept doing what they had always done. Quotations built by hand in a spreadsheet. Schedules that lived in one person's head. Customers who found out where their shipment was by picking up the phone and asking. Annual maritime trade through these waters runs into tens of billions of dollars, yet the tools running it were held together with good memory and goodwill.

Complexity you can learn from

There is a practical upside to starting somewhere this demanding. Every voyage a fleet completes here teaches the platform something about real sea conditions, real ports, and real routes. Depth, current, weather, and the judgment of captains who have sailed these waters for years, all of it feeds back into a system that gets more accurate the more it is used.

That kind of learning only happens where the conditions are genuinely difficult. A platform trained on calm, predictable routes never has to get smart. Ours had no choice.

Built here, not only for here

None of this means the platform only works in Indonesian waters. Ports, currencies, tax rules, and document templates are all configurable, not hardcoded to one country. An operator running routes out of Rotterdam configures the system the same way a fleet in Surabaya does. We just happened to build the foundation in the place where the sea asks the most of you.

If you can serve the world's most complicated archipelago well, serving anywhere else becomes a lot more straightforward. That was the bet. So far, it has paid off.