# apitable vs Web Rendering Proxy (WRP)

> Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.

| | apitable | Web Rendering Proxy (WRP) |
|---|---|---|
| Score | 65/100 ✓ | 53/100 |
| Rank in category | #4 of 17 in Low Code | #11 of 25 in Proxy |
| GitHub stars | 15 654 ✓ | 1 306 |
| Stars, last 30 days | +35 ✓ | +0 |
| Stable releases, 12 months | 0 | 4 ✓ |
| Latest release | — | 4.10.3 · 23 Apr 2026 |
| Setup | Moderate | Easy ✓ |
| Official Docker image | Yes | Yes |
| License | AGPL-3.0 | Apache-2.0 |
| Main language | Typescript | Go |

## Which one should you pick?

apitable scores 65/100 against 53/100 for Web Rendering Proxy (WRP), so it is the safer default.

Web Rendering Proxy (WRP) ships more often: 4 stable releases in the past year, against 0 for apitable.

If you want the quickest setup, Web Rendering Proxy (WRP) is easier to run; apitable needs more configuration.

apitable is growing faster right now (+35 stars in 30 days).

## Details

- [apitable](https://selfhost.directory/project/apitable) (markdown: https://selfhost.directory/project/apitable.md)
- [Web Rendering Proxy (WRP)](https://selfhost.directory/project/wrp) (markdown: https://selfhost.directory/project/wrp.md)

---
Source: https://selfhost.directory/compare/apitable-vs-wrp