product-apim
Welcome to the WSO2 API Manager source code! For info on working with the WSO2 API Manager repository and contributing code, click the link below.
Runssource: GitHubhomepageJavaApache-2.0commit 9e253b10599c
Java, Apache-2.0 licensed. The project labels itself: api gateway, api management, apis, gateway, microservices, rest and synapse.
product-apim runs. An Argusic agent installed it in 66 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
WSO2 API Manager v4.7.0 built from source via Maven and running on localhost:9443, serving Publisher (302 redirect) and Developer Portal (302 redirect) web applications, with all 4 sub-modules (api-control-plane, gateway, traffic-manager, all-in-one-apim) producing distribution zips
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 50 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- JDK 21 not found on system - JAVA_HOME unset, no JDK anywhere in filesystem2 minutes
- Maven not found on system - mvn command not available2 minutes
- unzip command not available for extracting archives
- Install time
- 66 minutes
- Cold machine to finish
- 67 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- ./bin/api-manager.sh --version returned 'WSO2 API Manager v4.7.0'; curl -sk https://localhost:9443/publisher returned HTTP 302 (redirect to login); curl -skL https://localhost:9443/publisher returned HTTP 200 (login page rendered); curl -sk https://localhost:9443/devportal returned HTTP 302
- Model tokens used
- 797,605
- Exact commit tested
- 9e253b10599c
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 2, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- Installed JDK 21 (Adoptium) and Maven 3.9.9 from scratch since neither was in the environment - Built all 4 modules (`api-control-plane`, `gateway`, `traffic-manager`, `all-in-one-apim`) via Ma… - Extracted the all-in-one distribution and launched the WSO2 API Manager server - Verified the server responds on `https://localhost:9443` tokens used 797,605 Here's my final report. **Work done:** - Installed JDK 21 (Adoptium) and Maven 3.9.9 from scratch since neither was in the environment - Built all 4 modules (`api-control-plane`, `gateway`, `traffic-manager`, `all-in-one-apim`) via Ma… - Extracted the all-in-one distribution and launched the WSO2 API Manager server - Verified the server responds on `https://localhost:9443`
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 66 minutes to install, slower than the median of the 31 comparable projects Argusic has measured.
Of the 32 api-gateway projects Argusic has installed and timed, product-apim was the 32nd fastest to reach a running state, and 22 of 32 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.29 | |
| Argusic Runner | 1/3 | Did not run | 0.00 | 0.01 |
Topics (from GitHub)
api-gatewayapi-managementapisgatewaymicroservicesrestsynapse
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/product-apim)Questions
- Does product-apim run?
- Yes. product-apim runs. Argusic installed and launched it on a clean machine in 66 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test product-apim?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 9e253b10599c. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test product-apim?
- The run that produced this verdict cost $0.29: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does product-apim take to install?
- 66 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does product-apim need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing product-apim?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does product-apim compare with the alternatives?
- Of the 32 api-gateway projects Argusic has installed and timed, product-apim was the 32nd fastest to reach a running state, and 22 of 32 reached one at all.
- Where is the evidence for product-apim?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.