# Apache Web Servers and Gateways for Small Business

HTTP Server can suit a capable owner. Tomcat and APISIX need IT help. Compare all eight projects, managed hosting prices and realistic running costs.

Author: J.A. Watte
Published: October 30, 2026
Source: https://jwatte.com/blog/apache-web-servers-api-gateways-small-business/

---

**Apache HTTP Server is worth considering if you have a capable helper and a reason to manage your own website host. Tomcat and APISIX belong with your IT provider; the other projects serve narrower application, file-transfer and caching jobs.**

The names sound similar because they sit near the front door of a website, but they do different work. HTTP Server serves web content. Tomcat runs Java web applications. An API gateway checks and routes requests going to applications behind it. A cache keeps reusable responses closer to visitors. None supplies your business website’s writing, booking process or stock system by itself.

For a small brochure site, a managed static host can remove a surprising amount of routine work. For an existing application, the software vendor’s supported setup usually matters more than a general server recommendation. For a gateway, first identify the request that needs controlling. Adding another service without a specific job creates another place for a routine update to interrupt the business.

October 30, 2026 update: added setup time and costs when an AI agent does the typing.

## Every project in this group

We checked the main release and installation pages on October 29, 2026. The catalog’s Tomcat entry names the supported 10.1 branch; the current project homepage also lists the newer 11.0.27 branch. Choose the one your application supports. The old mod_ftp beta is included for completeness. We would not choose it for a new deployment.

| Project | What it does | Who runs it | Latest release and date |
|---|---|---|---|
| [Apache Apisix](https://apisix.apache.org) | Controls and routes requests to application interfaces. | Your IT department or provider | [3.19.0; 2026-09-28](https://apisix.apache.org/downloads/) |
| [Apache FtpServer](http://mina.apache.org/ftpserver-project) | Hosts a configurable FTP file transfer service. | Your IT department or provider | [1.2.1; 2025-05-01](https://github.com/apache/mina-ftpserver/releases/tag/ftpserver-parent-1.2.1) |
| [Apache HTTP Server](https://httpd.apache.org/) | Serves websites and forwards web requests to business applications. | You, with a capable helper | [2.4.69; 2026-10-01](https://httpd.apache.org/download.cgi) |
| [Apache mod_ftp](https://httpd.apache.org/mod_ftp/) | Adds FTP file transfer support to Apache HTTP Server. | Your developer | [0.9.6-beta; 2008-10-08](https://httpd.apache.org/download.cgi) |
| [Apache Shenyu](https://shenyu.apache.org) | Routes application requests and applies access, traffic and monitoring controls. | Your IT department or provider | [2.7.1; 2026-07-08](https://github.com/apache/shenyu/releases/tag/v2.7.1) |
| [Apache Tomcat](http://tomcat.apache.org/) | Runs Java web applications on a server. | Your IT department or provider | [11.0.27; supported 10.1 branch: 10.1.61; 2026-10-12](https://tomcat.apache.org/) |
| [Apache TomEE](http://tomee.apache.org) | Runs Java business applications with the additional services they need. | Your IT department or provider | [10.2.0; 2026-07-17](http://tomee.apache.org/downloads.html) |
| [Apache Traffic Server](https://trafficserver.apache.org) | Caches web content and forwards requests to reduce load on websites. | Your IT department or provider | [10.2.1; 2026-10-20](https://trafficserver.apache.org/) |

## HTTP Server: a small site you can maintain yourself

[Apache HTTP Server](https://httpd.apache.org/) accepts browser requests and serves files or passes selected requests to another application. For an ordinary site made of HTML, images and style sheets, a maintained operating-system package can be a reasonable owner/helper project. The helper needs to know how to update the machine, configure the domain, renew TLS certificates and recover the site after a mistake.

For example, a four person plumbing company might have a simple service-area website whose changes wait for an outside webmaster. A capable helper could place the static site on HTTP Server and give the owner a documented publishing process. On a normal Monday, the owner corrects an opening time and knows how to verify that visitors see the change. Our operating allowance is $92 to $229/month plus $272 to $817 setup. That does not include designing an editing interface, writing pages or improving search rankings.

For example, a coffee shop with two locations and twelve employees might want one place to publish menus and holiday hours. The helper could host static pages and keep both locations in the same versioned content project. Staff update the menu once and check both location pages. The same server budget applies only to the modest traffic case below. HTTP Server does not include a menu editor; if the owner cannot publish confidently, a managed site builder or a developer-maintained workflow may fit better.

The [2.4 installation guide](https://httpd.apache.org/docs/2.4/install.html) recognizes operating-system packages as well as source builds. Its source-build estimate is at least 200 MB temporary disk and about 50 MB installed, before content and modules. Those figures are not the size of a usable business server. The guide does not establish a universal RAM or CPU floor. We assume one Small server with 2 vCPU, 4 GiB RAM and 80 GiB disk for a modest static site, subject to testing. Prefer maintained packages and their security updates over compiling a release merely to get a familiar version number.

The [current release page](https://httpd.apache.org/download.cgi) lists 2.4.69, October 1, 2026. Package maintainers may backport fixes without matching that exact upstream number; check the package’s security notices. The [TLS guide](https://httpd.apache.org/docs/2.4/ssl/ssl_howto.html) explains certificate and key configuration. Keep private keys confidential, and document how certificates can be reissued. A backup containing only the public website files leaves out part of recovery.

For this static-site comparison, [Netlify Personal](https://www.netlify.com/pricing/) lists $9/month with 1,000 credits, checked October 29. Our low and high workload assumptions are two to four production deploys, 5 to 10 GB transferred and 20,000 to 50,000 web requests/month, with no functions or compute. At 15 credits/deploy, 20/GB and 2 per 10,000 requests, those cases use 134 and 270 credits. Both fit the plan. The managed service hosts the static output; it does not replace arbitrary Apache modules or a PHP application.

Our self hosted case assumes one server, 10 to 50 GB retained backups, 4 to 12 setup hours and 1 to 3 administration hours/month. Content work is common to both routes and excluded. We assume no incremental managed-platform setup charge in the worksheet; migration and account configuration still need someone’s time.

| HTTP Server static site | Low labor/workload | High labor/workload |
|---|---:|---:|
| Setup labor | $272 | $817 |
| Monthly self hosted | $92 | $229 |
| Self hosted, 36 months | $3,588 | $9,045 |
| Netlify Personal, monthly | $9 | $9 |
| Netlify Personal, 36 months | $324 | $324 |
| Self hosting savings, 36 months | Negative $3,264 | Negative $8,721 |
| Break even month | Never | Never |

Self hosting never breaks even against that managed platform charge. It can still make sense when the owner is learning, an existing maintained machine already serves another justified job, or a specific application requires it. Count the incremental workload in those cases instead of pretending that a server already paid for takes no care. For a fresh brochure site, the managed option is the easier financial case here.

Start with the official installation and TLS documentation, using the distribution’s maintained package route. Publish a disposable copy first, test one content update and restore the previous version. Confirm that the owner can reach support if the helper is away. Skip self hosting when nobody will notice a failed certificate renewal before a customer does.

## Tomcat: the runtime your Java application asks for

[Tomcat](https://tomcat.apache.org/) runs Java web applications. It is not an inventory app, a booking product or a content-management system. Its business value comes from an application that already runs on it, with a maintainer who can identify the required Tomcat branch and Java runtime.

For example, a twelve person machine shop might already own a Java job-status portal that staff use to answer customer calls. Its provider could run the supported application on a dedicated Tomcat instance and test upgrades against a copy of the job data. On a normal day, the office looks up the current job stage instead of walking onto the shop floor. Our bounded host budget is $92 to $229/month plus $272 to $817 setup; the application license, database and vendor support remain separate.

For example, an eight person print shop might have a custom proof-approval application that uses Tomcat. Its developer could package the existing application with a documented Java runtime and store uploaded files in a separately backed-up location. Staff would see which proof was approved and avoid confusing an earlier version with the final one. The same operating range applies only if the application fits the assumed host. Storage for large files, application fixes and customer-facing support are outside it.

The [Tomcat 11 setup page](https://tomcat.apache.org/tomcat-11.0-doc/setup.html) requires Java 17 or later and provides a Windows service installer as well as Unix guidance. [Tomcat 10.1 setup](https://tomcat.apache.org/tomcat-10.1-doc/setup.html) uses Java 11 or later. These requirements belong to different branches. Moving from an older Java application to a newer Jakarta-based stack may require code changes; upgrading the runtime is not a substitute for asking the application vendor about compatibility.

Neither setup page gives a universal business workload RAM minimum. Our assumption is one Small 4 GiB host with 2 vCPU, an explicit outage window and a workload test. A Java process can consume the memory you allow it, while the operating system and other processes need room too. Have the provider record expected concurrency and heap limits, then test a slow dependency or failed database connection. A process that starts successfully has not passed a recovery test.

The latest major download is [11.0.27](https://tomcat.apache.org/download-11.cgi), dated October 12, 2026; 10.1.61 remains the catalog’s supported branch on that date. Pin the application’s supported branch and update within it according to its security guidance. Run the service with limited privileges, keep management interfaces private and patch the Java runtime and application dependencies as well as Tomcat itself.

[Render pricing](https://render.com/pricing), read October 29, lists a Pro workspace at $25/month plus compute. Its 2 CPU, 4 GB instance is $85/month, giving $110/month for our comparison. Its [Docker documentation](https://render.com/docs/docker) supports packaging a Java application in a container. Render maintains the platform; your developer still maintains the container image, JVM and application. Persistent disks cost extra, so this example assumes application state lives in a separately priced service on either route.

We use the same 4 to 12 setup hours, 1 to 3 monthly administration hours and 10 to 50 GB backup allowance for the self hosted runtime. This is the infrastructure slice of the decision, with application development, database service and common application maintenance excluded on both sides. It is not a quote for fully supported business software.

| Tomcat application host | Low labor/workload | High labor/workload |
|---|---:|---:|
| Setup labor | $272 | $817 |
| Monthly self hosted | $92 | $229 |
| Self hosted, 36 months | $3,588 | $9,045 |
| Render platform, monthly | $110 | $110 |
| Render platform, 36 months | $3,960 | $3,960 |
| Self hosting savings, 36 months | $372 | Negative $5,085 |
| Break even month | 16 | Never |

The low self hosted case saves $372 over 36 months and breaks even in month 16. The high case costs $5,085 more and never breaks even. A modest difference in monthly administration overwhelms the apparent bargain. A provider quote should therefore identify runtime updates and application work separately, including the work that remains on the managed platform.

Skip a new Tomcat installation if the software vendor already offers a supported hosted version at an acceptable total cost. Start by obtaining its support matrix and recovery instructions, then use the matching official setup page. Keep a copy of the last working application and configuration. A rollback that cannot read data written by the new application is not a usable rollback.

## APISIX: control requests to applications you already have

[Apache APISIX](https://apisix.apache.org/) is an API gateway. It can route requests and apply configured controls before they reach a backend. An owner meets it when several integrations need a common entry point or a provider wants consistent authentication and traffic limits. It does not supply the order, stock or delivery applications behind those routes.

For example, a six person online parts retailer might let a supplier integration query stock availability. Its provider could put a gateway before the existing stock API, issue a separate credential and limit that integration’s request rate. On a normal day, a misbehaving supplier client would be visible in gateway logs rather than simply making the store slow. The one-gateway operating allowance below is $92 to $229/month plus $272 to $817 setup, with backend development and security design quoted separately.

For example, a nine person delivery service might need its dispatch application and customer-tracking page to reach the right backend version during an update. A provider could configure routes and test the change before moving traffic. Dispatchers would keep using the same address while the provider controls which backend serves requests. The same budget applies to a small standalone gateway with an agreed outage window. It does not buy a redundant regional gateway service.

The [official quick start](https://apisix.apache.org/docs/apisix/getting-started/README/) uses Docker and starts APISIX with etcd. It also disables Admin API authorization for its demonstration. Do not copy that setup onto a public business server. The [installation guide](https://apisix.apache.org/docs/apisix/installation-guide/) separates production concerns, including protecting management interfaces. The current [download page](https://apisix.apache.org/downloads/) lists 3.19.0, September 28, 2026.

For our deliberately small example, the [deployment-mode documentation](https://apisix.apache.org/docs/apisix/deployment-modes/) describes standalone configuration from a file without etcd. One gateway is the smallest bounded topology we price. The cited installation pages publish no universal CPU or RAM minimum; one Small 4 GiB host is our allowance pending a load test. If the provider needs a control plane, etcd cluster or multiple gateways, price those nodes and the cluster administration range instead. Keep its admin and control ports outside public reach.

[Amazon API Gateway pricing](https://aws.amazon.com/api-gateway/pricing/), read October 29, supplies a complete REST example we can reproduce: five million requests/month × $3.50/million = $17.50, plus 14.3 GB response transfer × $0.09 = $1.29, for $18.79/month. The example applies to the listed regions including US East (N. Virginia) and US West (Oregon). Our low and high cases hold this workload fixed and vary labor. Backend compute, logging and other AWS services remain extra. It is an alternative gateway service with different configuration and plugin capabilities.

| APISIX standalone gateway | Low labor/workload | High labor/workload |
|---|---:|---:|
| Setup labor | $272 | $817 |
| Monthly self hosted | $92 | $229 |
| Self hosted, 36 months | $3,588 | $9,045 |
| AWS gateway example, monthly | $19 | $19 |
| AWS gateway example, 36 months | $676 | $676 |
| Self hosting savings, 36 months | Negative $2,911 | Negative $8,368 |
| Break even month | Never | Never |

Self hosting never breaks even against that platform charge. A specific plugin, an existing operating team or a local-network requirement may justify APISIX, but those need a written reason. [API7’s pricing page](https://www.api7.ai/pricing) offers custom quotes for its commercial product and support; no fixed price was verified, and we have not invented one. Ask whether a quote covers private deployment, hosted operation or support only.

Start with a private example route and a harmless backend. Have the provider test an invalid credential, a slow backend and a configuration rollback. Verify that logs omit secrets. Skip the gateway when a single application already has suitable authentication and there is no routing or policy problem to solve.

## How we counted the cost

The shared method uses $68.09 per administration hour, an employee compensation estimate from [BLS wages](https://data.bls.gov/oesprofile/?areas=INDUSTRY,STATE,MSA&major_group=150000&measure=01&occupation=151244&year=2025) divided by the [70.0% wages share](https://data.bls.gov/timeseries/CMU2020000000000P). An outside IT provider bills more than this proxy, so get a quote. [DigitalOcean](https://www.digitalocean.com/pricing/droplets) supplies our Small server at $24/month (2 vCPU, 4 GiB RAM, 80 GiB disk), Medium at $48 (4 vCPU, 8 GiB, 160 GiB), and Large at $252 (8 dedicated vCPU, 32 GiB, 100 GiB). These are monthly caps without an annual commitment. [Backblaze B2](https://www.backblaze.com/cloud-storage/pricing) costs $6.95 per decimal TB/month after the first 10 GB free. All were checked October 29, 2026.

Setup = hours × $68.09. Monthly self hosted = server charges + max(0, retained backup GB minus 10) × $0.00695 + administration hours × $68.09. The 36 month total adds setup to 36 monthly bills; savings subtract that total from the alternative. Break even is setup divided by positive monthly savings, rounded up; otherwise it is never. Calculations retain cents internally and display whole dollars.

Our assumptions are 4 to 12 setup hours and 1 to 3 administration hours/month for a bounded single server, or 24 to 60 and 6 to 16 for a small cluster. These exclude application development, migration, training, incidents and on call coverage on both sides. Alternative setup is assumed zero incremental infrastructure labor in these examples. Implementation still takes work. Backup volumes include retained copies. We assume no chargeable backup requests or excess transfer; add them if your usage exceeds the provider allowances. Low and high cases are planning ranges to replace with measured requirements.

## Setup time when Claude or ChatGPT does the typing

We keep the HTTP Server static-site example: one $24 Small server and 10 to 50 GB of backups. Our assumed hours include prompting, review, testing and corrections, not unattended agent runtime. Coding studies do not validate these Apache setup savings. [55]

| HTTP Server: paired planning cases | Low | High |
|---|---:|---:|
| Manual setup hours | 4 | 12 |
| AI setup share; hours | 50%; 2 | 80%; 9.6 |
| Manual administration hours/month | 1 | 3 |
| AI administration share; hours/month | 75%; 0.75 | 100%; 3 |
| Manual total, 36 months | $3,588 | $9,045 |
| Claude Pro subscription total, 36 months | $3,039 | $9,081 |
| ChatGPT Plus subscription total, 36 months | $3,039 | $9,081 |
| API pay per token: Claude Opus 5.5 total, 36 months | $2,853 | $8,995 |
| API pay per token: GPT-6 Astra total, 36 months | $2,876 | $9,166 |
| Opus setup/monthly token charges | $0.764 / $0.382 | $6 / $3 |
| Astra setup/monthly token charges | $1.970 / $0.985 | $15 / $7.50 |

Let S/A be manual setup/monthly hours, q/r the AI shares, H monthly hosting plus backups, and T0/Tm setup/monthly tool charges. We use $68.09/hour and round totals only after calculation.

```text
Manual total = S × $68.09 + 36 × (H + A × $68.09)
AI total = S × q × $68.09 + T0 + 36 × (H + A × r × $68.09 + Tm)
Savings = Manual total minus AI total
```

We budget Claude Pro or ChatGPT Plus at $20 for a separate setup month, then $5/month for 36 operating months: a 25% allocation only when other work uses the rest. Without sharing, add $540. Equal prices do not mean equal allowances; check limits and price extra usage. [43, 44, 45]

Our assumed API budgets are 200,000 to 1,000,000 input and 20,000 to 100,000 output tokens for setup; monthly, 100,000 to 500,000 input and 10,000 to 50,000 output. Low input splits 30% ordinary, 10% short cache writes and 60% reads; high input is uncached. Charges include retries and billed reasoning. The kit shows rates and token arithmetic. [52, 53, 54]

Claude Code or Codex can draft virtual-host configuration and certificate checks. Desktop Commander, connected to the server, can install HTTP Server, edit its configuration and read error logs. Claude in Chrome can inspect Cloudflare DNS and the provider panel while we supervise. [46, 48, 49, 50] ChatGPT’s supported cloud browser is separate from your Chrome session, not a promised equivalent extension. [51]

Our base uses free local Desktop Commander or Codex CLI. Optional Remote Pro adds $20 in setup and $5/month with the same allocation, or $200 overall. [47]

Use a new or staging server, keep secrets out of chat and approve commands or use a restricted sandbox. Watch browser actions; use subscriptions for supervised supported tools and API keys for custom automation. Review every change and test a site restore and certificate renewal; we still own backups, updates and the decision.

The conclusion stays: Netlify Personal’s $324 over 36 months costs less in every case. AI assistance does not make this brochure site cheaper to self host. The high case saves no monthly labor; recurring fees can erase setup savings.

## Needs your IT department or a provider

The monthly hours below are our planning assumptions: 1 to 3 for a small single host and 6 to 16 for a multi-component cluster. They exclude application development and incidents. None of these projects should be selected solely because its license has no purchase charge.

**FtpServer.** This runs a file-transfer service, often for an existing supplier requirement. The [standalone guide](https://mina.apache.org/ftpserver-project/running_ftpserver_standalone.html) describes a Java service on one host but contains old example filenames and permissive demo accounts. Use a current release and a reviewed configuration; no universal RAM minimum was established. FTP, FTPS and SFTP are different protocols, so confirm the actual requirement. An eight person print shop receiving supplier artwork through FTPS might justify it, allowing 1 to 3 hours/month for accounts, TLS, permissions, quotas and recovery. [AWS Transfer Family](https://aws.amazon.com/aws-transfer-family/pricing/) publishes an FTPS example at $0.30/endpoint-hour plus $0.04/GB transferred. At an assumed 720-hour month the endpoint alone is $216, with storage and other AWS services extra. The managed service still needs account and file-permission design.

**ShenYu.** This gateway fits teams already working with its application and plugin ecosystem. Its [Docker deployment](https://shenyu.apache.org/docs/deployment/deployment-docker/) uses separate administration and gateway processes; the [preparation guide](https://shenyu.apache.org/docs/deployment/deployment-before/) includes a database. A demonstration can use H2, but a durable production control plane needs a supported database and protected network access. No universal hardware floor was established. A ten person distributor with existing Java warehouse integrations might evaluate it with its provider. Budget 6 to 16 hours/month for a small multi-component deployment. Amazon API Gateway’s $18.79 published REST scenario above is a priced alternative for a suitable request workload. Plugin compatibility must be assessed separately. Ask which ShenYu-specific capability earns the added operational work.

**TomEE.** This adds Jakarta EE services around Tomcat. The [download page](https://tomee.apache.org/downloads.html) identifies 10.2.0, July 17, 2026, with Java 17 or later. Its 11.0.0-M1 is a milestone limited to evaluation. A single Java application host is the smallest starting point; database and memory needs depend on the application, and archive size is not a RAM requirement. A fifteen person manufacturer whose supplier portal requires these services should follow its vendor’s support matrix. Allow 1 to 3 administration hours/month for a bounded host, with application support separate. Render’s $110 Pro-plus-4-GB platform example above can host a suitable container, while the vendor’s own hosted application deserves a separate quote. Do not buy an enterprise runtime before identifying the feature the application uses.

**Traffic Server.** This is an HTTP proxy and cache. The [minimal reverse-proxy guide](https://docs.trafficserver.apache.org/en/latest/getting-started/index.en.html) can run one instance, even beside the origin, but that adds no host redundancy. Cache size, traffic and response behavior determine hardware needs; no universal minimum was verified. A seven person ecommerce brand might cache public catalog images while keeping customer accounts and carts out of the shared cache. Allow 1 to 3 administration hours/month for a small proxy and test cache rules before enabling it. [Cloudflare Pro](https://www.cloudflare.com/plans/) lists $25/month billed monthly or $20/month billed annually, with a managed global edge service. Origin hosting stays extra. Traffic Server’s [homepage](https://trafficserver.apache.org/) dates 10.2.1 to October 20, 2026; its download card retains an older date, so we use the homepage announcement.

## Your developer’s toolbox

**mod_ftp** adds FTP handling to HTTP Server. The [official page](https://httpd.apache.org/mod_ftp/) and download listing identify the old 0.9.6 beta. A developer integrates this module into an existing server stack. If it appears in an old configuration, ask the maintainer whether it is needed and supported before carrying it into a new machine. Do not mistake being listed in a catalog for evidence of recent maintenance.

## Risks and support

For HTTP Server, watch [2.4 vulnerabilities](https://httpd.apache.org/security/vulnerabilities_24.html). For Java applications, watch [Tomcat security](https://tomcat.apache.org/security.html). For gateways, read [APISIX security](https://apisix.apache.org/docs/general/security/) as well as the [ASF guidance](https://www.apache.org/security/). Keep management interfaces private, remove sample accounts and record who receives update notices. A publicly reachable login screen is not a reason to expose the rest of an administration service.

Back up the material needed to reconstruct the service: site content or application package, configuration, access policy and a safe way to recover credentials. Application data may live elsewhere and needs its own restore procedure. For caches, test that confidential responses never become shared content. For gateways, test the route and permission rules after every material change. For file transfer, test both the intended upload and a denied attempt outside the account’s area.

Read release dates alongside supported-version notices, mailing-list activity and the [Apache Attic](https://attic.apache.org/). An old module and a maintained runtime should not share the same automatic upgrade policy. A software vendor can also restrict which upstream release it supports, so coordinate security fixes rather than replacing the stack blindly.

The managed vendors linked here publish their own commercial services. API7 offers a quote; Render and Netlify sell platform hosting; AWS sells gateway and transfer services. Those contracts do not automatically cover your separately hosted Apache stack or application bugs. Ask a provider to name the layers it maintains and the ones you still own.

The [Apache License 2.0](https://www.apache.org/licenses/LICENSE-2.0) allows commercial use and modification under its terms, including notice obligations when redistributing. It supplies no warranty and does not grant the right to present your company as Apache. A license charge of zero does not include an operator or response-time commitment.

## Download the kit

The [web servers and API gateways kit](/downloads/apache-web-servers-api-gateways-small-business-kit.md) contains an HTTP Server first-week plan, a provider card for each IT project, the full table and the filled cost comparisons.

## Related reading

- [The Apache small business series](/blog/apache-open-source-projects-small-business/).
- [Websites, CMS and web applications](/blog/apache-websites-cms-web-apps-small-business/).
- [Security, identity and remote access](/blog/apache-security-identity-remote-access-small-business/).
- [Databases for business applications](/blog/apache-databases-small-business/).
- [Building and caring for a self hosted server](/blog/self-hosted-ai-server-from-scratch/).

## Fact-check notes and sources

Official pages and the series catalog evidence were read October 29, 2026. Prices are US dollars before tax; billing terms appear with each comparison. We have not installed these projects for this series.

1. [Apache Apisix](https://apisix.apache.org). Read October 29, 2026, 21:12:51 UTC (catalog observation).
2. [3.19.0; 2026-09-28](https://apisix.apache.org/downloads/). Read October 29, 2026, 21:37:26 UTC.
3. [Apache FtpServer](http://mina.apache.org/ftpserver-project). Read October 29, 2026, 21:38:18 UTC.
4. [mina-ftpserver release ftpserver-parent-1.2.1 on GitHub](https://github.com/apache/mina-ftpserver/releases/tag/ftpserver-parent-1.2.1). Read October 29, 2026, 21:22:49 UTC (catalog observation).
5. [Apache HTTP Server](https://httpd.apache.org/). Read October 29, 2026, 21:13:38 UTC (catalog observation).
6. [2.4.69; 2026-10-01](https://httpd.apache.org/download.cgi). Read October 29, 2026, 21:37:26 UTC.
7. [Apache mod_ftp](https://httpd.apache.org/mod_ftp/). Read October 29, 2026, 21:13:39 UTC (catalog observation).
8. [Apache Shenyu](https://shenyu.apache.org). Read October 29, 2026, 21:13:45 UTC (catalog observation).
9. [shenyu release v2.7.1 on GitHub](https://github.com/apache/shenyu/releases/tag/v2.7.1). Read October 29, 2026, 21:16:26 UTC (catalog observation).
10. [Apache Tomcat](http://tomcat.apache.org/). Read October 29, 2026, 21:37:26 UTC.
11. [Apache TomEE](http://tomee.apache.org). Read October 29, 2026, 21:39:49 UTC.
12. [10.2.0; 2026-07-17](http://tomee.apache.org/downloads.html). Read October 29, 2026, 21:38:20 UTC.
13. [Apache Traffic Server](https://trafficserver.apache.org). Read October 29, 2026, 21:42:01 UTC.
14. [2.4 installation guide](https://httpd.apache.org/docs/2.4/install.html). Read October 29, 2026, 21:37:27 UTC.
15. [TLS guide](https://httpd.apache.org/docs/2.4/ssl/ssl_howto.html). Read October 29, 2026, 21:37:29 UTC.
16. [Netlify Personal](https://www.netlify.com/pricing/). Read October 29, 2026, 21:37:26 UTC.
17. [Tomcat 11 setup page](https://tomcat.apache.org/tomcat-11.0-doc/setup.html). Read October 29, 2026, 21:37:27 UTC.
18. [Tomcat 10.1 setup](https://tomcat.apache.org/tomcat-10.1-doc/setup.html). Read October 29, 2026, 21:38:22 UTC.
19. [11.0.27](https://tomcat.apache.org/download-11.cgi). Read October 29, 2026, 21:38:54 UTC.
20. [Render pricing](https://render.com/pricing). Read October 29, 2026, 21:37:26 UTC.
21. [Docker documentation](https://render.com/docs/docker). Read October 29, 2026, 21:38:24 UTC.
22. [official quick start](https://apisix.apache.org/docs/apisix/getting-started/README/). Read October 29, 2026, 21:37:27 UTC.
23. [installation guide](https://apisix.apache.org/docs/apisix/installation-guide/). Read October 29, 2026, 21:38:23 UTC.
24. [deployment-mode documentation](https://apisix.apache.org/docs/apisix/deployment-modes/). Read October 29, 2026, 21:37:29 UTC.
25. [Amazon API Gateway pricing](https://aws.amazon.com/api-gateway/pricing/). Read October 29, 2026, 21:37:30 UTC.
26. [API7’s pricing page](https://www.api7.ai/pricing). Read October 29, 2026, 21:37:27 UTC.
27. [BLS wages](https://data.bls.gov/oesprofile/?areas=INDUSTRY,STATE,MSA&major_group=150000&measure=01&occupation=151244&year=2025). Read October 29, 2026, 21:12:08 UTC.
28. [70.0% wages share](https://data.bls.gov/timeseries/CMU2020000000000P). Read October 29, 2026, 21:17:59 UTC.
29. [DigitalOcean](https://www.digitalocean.com/pricing/droplets). Read October 29, 2026, 21:10:42 UTC.
30. [Backblaze B2](https://www.backblaze.com/cloud-storage/pricing). Read October 29, 2026, 21:10:42 UTC.
31. [standalone guide](https://mina.apache.org/ftpserver-project/running_ftpserver_standalone.html). Read October 29, 2026, 21:39:15 UTC.
32. [AWS Transfer Family](https://aws.amazon.com/aws-transfer-family/pricing/). Read October 29, 2026, 21:37:31 UTC.
33. [Docker deployment](https://shenyu.apache.org/docs/deployment/deployment-docker/). Read October 29, 2026, 21:37:29 UTC.
34. [preparation guide](https://shenyu.apache.org/docs/deployment/deployment-before/). Read October 29, 2026, 21:38:19 UTC.
35. [minimal reverse-proxy guide](https://docs.trafficserver.apache.org/en/latest/getting-started/index.en.html). Read October 29, 2026, 21:37:29 UTC.
36. [Cloudflare Pro](https://www.cloudflare.com/plans/). Read October 29, 2026, 21:37:30 UTC.
37. [2.4 vulnerabilities](https://httpd.apache.org/security/vulnerabilities_24.html). Read October 29, 2026, 21:38:26 UTC.
38. [Tomcat security](https://tomcat.apache.org/security.html). Read October 29, 2026, 21:38:55 UTC.
39. [APISIX security](https://apisix.apache.org/docs/general/security/). Read October 29, 2026, 21:38:57 UTC.
40. [ASF guidance](https://www.apache.org/security/). Read October 29, 2026, 21:39:57 UTC.
41. [Apache Attic](https://attic.apache.org/). Read October 29, 2026, 22:09:30 UTC.
42. [Apache License 2.0](https://www.apache.org/licenses/LICENSE-2.0). Read October 29, 2026, 21:39:56 UTC.

43. [Claude plans](https://claude.com/pricing). Read October 29, 2026, 23:31:08 UTC; reused for this update.
44. [ChatGPT plans](https://chatgpt.com/pricing/). Read October 29, 2026, about 23:27 UTC in a regular browser.
45. [Codex plan access](https://help.openai.com/en/articles/11369540-using-codex-with-your-chatgpt-plan). Read October 29, 2026, 23:31:16 UTC; reused for this update.
46. [Codex CLI](https://developers.openai.com/codex/cli). Read October 29, 2026, 23:32:01 UTC; reused for this update.
47. [Desktop Commander pricing](https://desktopcommander.app/pricing/). Read October 29, 2026, 23:31:08 UTC; reused for this update.
48. [Desktop Commander setup and permissions](https://raw.githubusercontent.com/wonderwhy-er/DesktopCommanderMCP/main/README.md). Read October 29, 2026, 23:31:41 UTC; reused for this update.
49. [Claude in Chrome](https://support.claude.com/en/articles/12012173-get-started-with-claude-in-chrome). Read October 29, 2026, 23:31:11 UTC; reused for this update.
50. [Chrome permissions](https://support.claude.com/en/articles/12902446-claude-in-chrome-permissions-guide). Read October 29, 2026, 23:31:09 UTC; reused for this update.
51. [ChatGPT cloud browser](https://help.openai.com/en/articles/20001280-using-cloud-browser-in-chatgpt). Read October 29, 2026, 23:32:01 UTC; reused for this update.
52. [Claude API pricing](https://platform.claude.com/docs/en/about-claude/pricing). Read October 29, 2026, 23:31:14 UTC; reused for this update.
53. [OpenAI API pricing](https://developers.openai.com/api/docs/pricing). Read October 29, 2026, 23:31:13 UTC; reused for this update.
54. [OpenAI prompt caching](https://developers.openai.com/api/docs/guides/prompt-caching). Read October 29, 2026, 23:32:00 UTC; reused for this update.
55. [METR coding study limitations](https://metr.org/blog/2026-02-24-uplift-update/). Read October 29, 2026, 23:31:09 UTC; reused for this update.

*Apache, the Apache feather logo and the Apache project names are trademarks of The Apache Software Foundation. This site is not affiliated with or endorsed by the ASF. Other product names are used for identification only.*


---

Canonical HTML: https://jwatte.com/blog/apache-web-servers-api-gateways-small-business/
RSS: https://jwatte.com/feed.xml
JSON Feed: https://jwatte.com/feed.json
Hero image: https://jwatte.com/images/apache-web-servers-api-gateways-small-business.webp