SideCar microservice

Pay for the WebDirect capacity you actually use.

WebDirect Auto-Scaling automatically adjusts your FileMaker WebDirect server capacity based on real user demand. Servers spin up when users connect and spin down when they disconnect - eliminating idle capacity and absorbing spikes without manual intervention. Multi-machine deployments have seen cost reductions of 80% or more.

The problem

Always-on WebDirect capacity is expensive idle time.

Most WebDirect deployments are sized for peak load. That means most of the time, most of the capacity is doing nothing - and when an unexpected spike hits, even peak-sized capacity can fall short. Auto-Scaling solves both problems with one architecture.

Concrete example

Consider a FileMaker app with 300 WebDirect users on a traditional always-on multi-machine deployment: roughly 48 hours per week of unused server capacity, with no mechanism to handle a sudden demand surge. Auto-Scaling eliminates the idle time and absorbs the surge - the same architecture solves both.

Key capabilities

What Auto-Scaling does for you.

Every capability is engineered for FileMaker WebDirect specifically - not a generic auto-scaling group bolted on after the fact.

Resources scale with users

When users connect, capacity comes online. When they disconnect, it scales back down. You stop paying for idle server time and you stop running out of capacity at peak.

Built for multi-machine deployments

Auto-Scaling is most powerful in multi-machine WebDirect topologies - exactly where always-on capacity is most expensive. Soliant.cloud customers have seen up to 80% cost reduction versus traditional always-on configurations.

Handles unpredictable spikes

If a marketing campaign, a regulatory deadline, or a public-facing form drives a sudden surge in WebDirect users, Auto-Scaling adds capacity automatically - no failed logins, no missed business.

AWS-native delivery

Delivered via AWS CloudFormation as infrastructure-as-code. The same automation patterns AWS itself uses, applied specifically to FileMaker WebDirect.

Use case

A 300-user WebDirect deployment, before and after.

The most dramatic savings come from multi-machine deployments where always-on capacity has been over-provisioned for months or years.

  1. A FileMaker app supporting 300 WebDirect users
  2. Traditional always-on capacity: ~48 hours per week of idle server time
  3. No mechanism to handle demand spikes - failed logins during campaigns
  4. With Auto-Scaling: capacity follows user demand, idle time is eliminated, spikes are absorbed automatically

If you’re running multi-machine WebDirect, Auto-Scaling almost certainly pays for itself. Let’s look at your numbers.

Get a Quote