We are the vendor here. By the rule this site argues for, anything a vendor says about its own product is a claim until you have seen it yourself. So this page does not score the product. It describes what the demo contains, so you know what you can check, and it lists what the demo cannot show. The checking is yours to do.
What kind of demo it is
In the terms of the formats guide, the Cargovate demo is a self-serve sandbox. It is the product running, not a click-through tour: what you enter is stored, and you can edit and delete it. It lives on its own address, cargovate.io, separate from the product site.
It is not a trial of the product. Cargovate has no self-service plan; working accounts are set up after a conversation, and an evaluation on your own data is arranged with the team. The demo is the look you can take before any of that, without talking to anyone.
Before you open it
The first item on the checklist is to read what a demo says about your data. The entry page of this one says three things, and they are the three to look for in any demo:
- You get your own private workspace, created when you register, visible only to you.
- It is deleted automatically after a few hours.
- You should not put anything real in it.
Registering asks for a name, an email address, a password and a company name, and for the kind of business you are. We registered on 9 October 2026 and were inside the workspace straight away, with no confirmation email and no call. The demo does not send email at all, so the address is only your sign-in name. Use invented details, as demo data and privacy recommends for any demo.
The first ten minutes
The workspace opens with sample data already in it, so the screens are not empty. When we checked, a new workspace held six shipments, each at a different stage: created, warehoused, at port, in transit, held at customs and delivered. It also held six parties, one of each kind a shipment involves: a shipper, a carrier, a warehouse, a freight forwarder, a consignee and a customs broker. Every company name in it is invented.
That is a small data set on purpose. Six shipments at six stages put something on every screen, where fifty random rows would look busier and show less. It also means the lists are short, which matters later.
The checklist says to work out what business the sample data describes. Here it is international freight: goods moving from a factory through ports, customs and a warehouse to a consignee. If your work looks like that, the vocabulary will be familiar. If you manufacture or run a fleet, choose that when you register, because of the next point.
There is a panel of guided tours. Each one points at the real buttons and waits while you use them, so a tour here is a prompt to operate the product, not a recording. Per the checklist, try your own task cold first and take a tour second.
What your choice at registration changes
The product is modular, and a demo workspace is given the modules that the kind of business you chose would use: warehousing for a warehouse or distributor, manufacturing for a manufacturer, maintenance for a fleet operator, custody for a carrier. If you open a part of the product your workspace does not have, the demo says so and tells you which choice would have included it. To look at a different module, start a second demo.
This is worth knowing in any modular product: the demo you are in may not be the whole product, and it may not be the configuration you would buy. Ask which modules your quote includes, and check that the demo you evaluated had the same ones.
Do your own task, then break it
Because the workspace is yours alone and is deleted anyway, the middle of the checklist can be done without restraint. Create a shipment with invented details. Move one of the sample shipments to a new status. Change a record and look for what the history says afterwards. Then do the section of deliberate mistakes: wrong values, a duplicate, a step out of order, a delete.
We are not going to tell you how those turn out. A vendor reporting that its own product passed is exactly the evidence this site tells you to discount, and you can find out in ten minutes. Write down what you saw.
Other people, and getting out
Three things exist in the demo that the checklist asks about, so you can test them rather than ask:
- A second user. You can invite someone into your workspace with a narrower role. The invitation is a code you pass on yourself; nothing is emailed. Use it to sign in as a restricted user in a private window and see what they can reach.
- An activity record. The workspace keeps a log of requests made in it, with the user, the time and the outcome. After you change something, look for your change there.
- An export of the whole workspace. It lists what it contains table by table and says what it leaves out. Run it and open the file, as the checklist says, before believing this sentence.
What this demo cannot prove
This is the list from what a demo hides, applied honestly to our own demo.
| Question | Why the demo cannot answer it | How to get the evidence |
|---|---|---|
| Scale | Six shipments. Every list is instant | Ask to see an environment at your volume |
| Your data | The sample was written to fit the product, and nothing real may go in | A guided evaluation on a sample of your own records |
| Integrations | The demo is connected to nothing. Carrier connections use a customer's own carrier credentials, which a demo does not have | Ask which connections exist, and test the one you need in a proof of concept |
| Email and alerts | The demo never sends mail, so you cannot see a notification arrive | Ask to see them in a customer-style environment |
| Many users | You can add users, but a workspace that lasts hours cannot show a team working for weeks | A pilot |
| Setup effort | The workspace arrives configured and seeded | Ask what a new customer does in the first month, and who does it |
| Support | Nobody is supporting you in a demo | Ask a real question through the contact page and see what comes back |
| Price | There is none in the demo | Pricing is published on the product site; ask for a written quote |
What to take from the example
Three things generalize from this demo to any other you open.
- Read the entry page as a specification. A demo that states whether your workspace is private, how long it lasts and whether it sends mail has answered the first checklist section for you. One that says nothing has told you something too.
- Find out what the demo left out. Modules, integrations, volume. The list above took us a few minutes to write because we know the answer. Any vendor can produce the same list for their demo if you ask.
- Use the freedom. A private, disposable workspace is the one place you can make every mistake at no cost. An evaluation that only follows the tour has wasted it.
When a demo has told you what it can, the remaining questions go to people. For the product described here, that means asking Cargovate for an evaluation on your own data. For any product, running a sales demo and a proof of concept plan cover what comes next.