Apelora

Design your applications. Control your infrastructure.

For platform and operations teams that run their own Linux servers. Draw an application once; Apelora Fabric sets up its network rules and addresses, runs it on your servers and handles failures.

Request a demo Start building
Try the designer on your machine
npm install && npm run dev
Needs Node.js 22 or newer. Mock data, nothing is deployed. All the steps
Early development: tested on a four-server lab, not yet on production hardware
Apelora Studio: a gateway connects to a load balancer, which connects to two NGINX web servers and on to a PostgreSQL database; a Grafana module reads from the database. Each cable is labelled with its protocol.
Apelora Studio, the designer. Sample data: the badge at the top reads "Mock · Design only", so nothing is deployed from this view.
  • 143modules to design with, in 9 categories. Seven deploy today.
  • 4servers in the lab it has been tested on, running Incus 7.0 LTS.
  • 16built-in alert rules, with signed webhooks.
  • 190+API operations, from one documented OpenAPI file.
  • AGPLopen source. No tracking, no cookies on this site.

From the drawing to the audit log.

Two screens and one control plane. Each result says how it was checked.

Design with guardrails

Drag modules onto a canvas and connect their typed ports. A link that cannot work is refused before anything is deployed, and a capacity check says whether the design fits your cluster.

Checked in a real browser
More about design Apelora Studio: a module's Properties window is open on the Ports tab, and the validation panel at the bottom left reports one error, that a web server's required input has no connection.

See the whole cluster in one place

Servers, health and every change in Fabric Console. Maintenance, joining servers and cluster settings show a preview before anything changes; every change is a job you can follow, retry or cancel.

Real Incus tested
More about operating Fabric Console, Servers: the cluster database with three of three voters answering and a safe majority, then four servers with status, database role, failure domain, Incus version and capacity.

Connections become rules

Each cable becomes an access rule and a stable service address. Deny by default: what you did not draw cannot talk.

Real Incus tested
How connections work

Access is explicit

Roles at organisation, project and application scope. A second person approves sensitive changes, and every change lands in an append-only audit log.

Not independently audited
How access works

Know before your users do

16 built-in alert rules for failed jobs, silent workers, offline servers and expiring certificates, plus metrics for your own monitoring.

Checked against stand-ins
About monitoring

When a server fails, you know what happens next.

Health is written in words, with the reason and the next step. Fabric restarts a module on another server only once it knows the first one has stopped.

  • Stopped first. A failed server is "fenced": proven stopped, so two servers never write the same disk.
  • Measured. A container with data ran again 144 to 155 seconds after its server was force-stopped, in three lab drills.
  • Virtual machines are not drilled yet. That is on the roadmap.
Real Incus testedVirtual machines: roadmap

More about recovery

Both modules are running.
  1. Detect
  2. Fence
  3. Restart
  4. Healthy
Illustration, not a screenshot and not a measurement: the animation is faster than a real recovery. In the lab, a container with data ran again 144 to 155 seconds after its server was force-stopped. Virtual machines are not drilled yet.

From drawing to running application.

Fabric owns the application: its design, connections, replicas and health. Incus, the open-source system that runs containers and virtual machines on a cluster, owns the servers. Fabric talks to Incus only through its documented API.

  1. Design

    Connect modules on a canvas in Studio.

  2. Plan

    See what would be created, resized or removed, and whether it fits.

  3. Deploy

    A worker creates the instances as durable jobs. A crash or a repeated request never makes duplicates.

  4. Operate

    Health, recovery, backups and the audit log run from the Console.

A design with a gateway, a web module with three replicas and a database with a volume. On three servers the web replicas run apart on the application's network behind one service address, and the database keeps its volume.
Illustration, not a screenshot: a design and the instances it becomes on three servers. Select it to open full size.

Start building in three steps.

The documentation takes you from nothing to a managed application, and is kept with the code.

  1. 1Try it on your machineThe designer in a minute, or the whole stack against a lab cluster. No hardware to buy.Open the guide
  2. 2Install on your serversPlan the servers and network, install Incus, then PostgreSQL, the control plane, the worker and the two screens.Open the guide
  3. 3Deploy and manageReview the plan, deploy, then start, shut down, stop or migrate from the Applications list.Open the guide

Browse all documentation: runbooks, concepts, reference and decisions

The software is free. The help is optional.

Apelora Fabric is open source under the GNU Affero General Public License (AGPL). Services add people and time, not features: the software is the same for everyone.

Community

Start here

Run it yourself.

FreeOpen source, AGPL-3.0

  • The complete software and source code
  • Step-by-step docs, runbooks and design decisions
  • Questions and bug reports in public on GitHub
Start building

Deployment

We set it up with you.

Request a quoteQuoted for your environment

  • Installation and configuration
  • Validation on your servers
  • Handover with runbooks
Request a quote

Support

Someone to ask.

Request a quoteA subscription with defined coverage

  • Help installing, upgrading and operating
  • Diagnosis from your logs and support bundle
  • Confirmed defects fixed in releases
Request a quote

Integration, training or a larger deployment? Ask about custom services. Compare what each option includes.

Tell us about your environment

How many servers, what storage and network, who needs access. We will tell you what Apelora does for that today and what it does not.

Request a demo Ask about deployment