Comparison

CargoSharks and Logistaas

The closest comparison on this list: cloud freight software, sold to forwarders our size, active in this region. So the differences are narrow and specific, which makes them worth writing down properly.

Open the live demo All comparisons What we do The home page

01 — What we agree on

Most of this comparison is agreement

Two cloud systems sold to forwarders the same size in the same region will do most of the same job, and pretending otherwise is how comparison pages lose the reader. Quoting, operations, documents and finance are table stakes and both of us clear them. So this page concedes the middle first, and then spends its length on the crescents — which are narrow, specific, and worth writing down properly.

This is the closest comparison on the list, and drawing it honestly means drawing the agreement at its real size. What is left over is narrow and specific, which is why it is worth writing down precisely rather than inflating.

02 — In their words

What they say about themselves

Logistaas calls itself a transportation management system and “freight forwarding software of the future”, and says forwarders in more than 80 countries use it. It names modules for sales and pricing, operations, finance, accounting and a customer portal, and it publishes offices in Amman and London.

Read from www.logistaas.com on 2026-08-25. If this has gone out of date, tell us and we will correct it.

02 — The case against us

Pick Logistaas if

This section comes before the next one on purpose. A comparison page that cannot name a reader who should buy the other product is not a comparison.

You want a vendor with live customers behind them — they say forwarders in more than 80 countries use it. We are in pilot. That is a real difference and it is the one we would weigh most heavily in your position.
You need a module we have not built. Our boundary is published on /what-we-do/ §07 — no warehouse module, no purchase-order management, no native mobile app.

03 — The case for us

Pick us if

Every point below is a mechanism you can check in the demo or in the source, rather than a promise.

Arabic and English are the same build, checked for parity on every commit — 2,727 interface strings in both, and every document the system issues exists in each.
The dinar keeps three decimal places from the database to the printed invoice. Money is decimal end to end and never a floating-point number.
Separation between branches and entities is a row-level policy in the database, not a filter in the application — 197 of them. A query written wrong returns nothing rather than somebody else’s shipments.
Nothing is deleted. Every change is stamped with who made it and when, by 80 audit triggers, and a superseded row is marked superseded and stays.
You can open the whole thing right now, on seeded data, with a sign-in for you, your customer and your agent, without talking to anybody.

The claim	Figure	How you check it
Transport modes	5	Sea FCL, sea LCL, air, road, rail and courier appear in the mode selector on any enquiry in the demo.
Row-level security policies	197	select count(*) from pg_policies where schemaname = 'public' — against any deployment, ours or yours. The policies are written by loops over the table registry, so a grep of the migration text counts the loops rather than the policies; pnpm test:db fails the build if any table lacks one.
Audit triggers	80	select count(*) from pg_trigger where tgname like '%\_audit' and not tgisinternal — attached by a loop rather than by a list, so a table added in a later migration is covered without anybody remembering to add it.
Interface strings, English and Arabic	2,727	pnpm lint runs check-messages.mjs, which fails the build if a key exists in one catalogue and not the other.
Decimal places on every dinar	3	Open any invoice in the demo. A system built for dollars and adapted shows two.
Minutes to check all of the above	~10	No sign-up and no call. That is the claim this whole page rests on.

KWD 100.000 of master cost, across three houses, by volume

HBL-221112.5 cbm

HBL-22127.25 cbm

HBL-22134.75 cbm

House	Driver	Exact share	Floored	Left-over fils	Posted
HBL-2211	12.5 / 24.5	51.020408	51.020	—	51.020
HBL-2212	7.25 / 24.5	29.591837	29.591	+0.001	29.592
HBL-2213	4.75 / 24.5	19.387755	19.387	+0.001	19.388
Total	24.5	100.000000	99.998	+0.002	100.000

Exact shares almost never land on whole fils, so two are left over once every share is floored. Dropping them loses money and spreading them creates it, so they go to the two largest fractional remainders — the same rule parliaments use to turn votes into seats. The last column sums to 100.000 exactly, which is what makes the margin on house eleven a number you can still defend six months later.

On the screen

The screen the argument above is made on

Receivables grouped by how late they are, largest exposure first — The crescents are where a comparison between two peers is decided, and this is one of them: every charge line stores its own rate and the moment it was taken, money is decimal from the database to the page, and the ageing is grouped by exposure rather than by invoice date. Open it yourself — no sign-up.

04 — The questions

Ask both of us these, and compare the answers

Our answers are already written, and beside each one is what a good answer sounds like from any vendor — including us. Somebody who takes this list to another vendor’s call and gets a better answer than ours should buy from them, which is what makes it worth publishing.

The question	Our answer	What a good answer sounds like
Is the Arabic a translation layer, or is it the same build?	The same build. Right-to-left is in the layout rather than added on top of it, and `pnpm lint` fails if a string exists in one language and not the other. Open the demo, press the language switch, and look at a delivery order.	A good answer names a mechanism — a parity check that fails a build, one catalogue rather than two, right-to-left in the layout. A weak one is “yes, we support Arabic” plus a screenshot. Ask to see a printed delivery order rather than a screen: that is where an added-on language shows first.
How many decimal places does an invoice in Kuwaiti dinars carry?	Three, everywhere, because the dinar has three. This is the single fastest way to find out whether a system was built for dollars and adapted.	“Three” should come back instantly and without conditions. Hesitation, or “it is configurable”, usually means money is a floating-point number somewhere and the decimals are a display setting — which is fine until a rounding difference lands on a reconciliation.
Whose database is it, and can I have a copy of my data on a Tuesday afternoon without asking?	PostgreSQL, and yes. The separation between customers is enforced by the database itself rather than by our application, which is also what makes the answer to the first half of that question boring.	Listen for a named engine and an export you can trigger yourself. “We can arrange an extract” is a different answer from “here is the button”, and the difference is what leaving costs you in three years.
What does it cost when volume doubles?	Ask every vendor this and ask for the answer in writing. Per-shipment and per-transaction pricing is normal in this category and is not a trick — but it is a different shape of bill from a flat one, and the difference shows up in year two rather than at signature.	Any pricing shape is defensible; a refusal to put the shape in writing is not. Ask for the figure at twice and five times today’s volume, in the contract rather than on a call — and ask us the same way.
Can I see it working, today, without a call?	Yes — demo.cargosharks.com, no sign-up. We think this question separates vendors more reliably than any feature question, which is why it is last.	The answer is yes or no, and both are legitimate. A demo that needs a discovery call first is a sales process rather than a fault — but it is also a reliable measure of how long a pilot will take to start.

There is no vertical scale, and that is deliberate — the shape is the whole content. Per-shipment pricing is normal in this category and is not a trick, but it is a different shape of bill, and the crossing point is the number worth asking every vendor to put in writing. Including us.

What you will not find on this page

A tick-and-cross grid. We know our product properly and theirs from the outside, and a grid written by one side is not a comparison — it is an argument with a table around it. Worse, it goes stale silently: every entry starts decaying the day it is published, and the person it misleads is your prospect while the person who looks foolish is you.

Ask us directly at [email protected]. You will get a written answer that cites what each vendor publishes itself, and where we do not know, you will get “we do not know”.