Deploy a database without a repository. Pick an engine, choose where it runs, and Loomplane creates a project, checks the plan and approves only the one creation you asked for. Then it backs it up on a schedule and proves the backups restore.
Two Xraph services are in the catalog. Deploy them next to your apps like any database, and link your services to them from the manifest.
A gateway written in Rust that routes HTTP traffic to your services. Services that speak FARP publish their own OpenAPI, AsyncAPI, gRPC or GraphQL schemas, and Octopus turns them into routes as they come and go.
A multi-tenant data fabric for Go. Every write commits once in Postgres with a versioned event, and a relay projects it to a FalkorDB graph, an Elasticsearch index, caches and live subscribers.
Back up now, or set a schedule from every hour to once a week. Each export uses the engine’s own backup client.
Restore any recovery point into an isolated copy and check that an application can connect, without touching the live database.
Recovery points stay until you say otherwise. Turn on a retention policy and preview what it would remove first.
Keep a second copy of a database in step on another server or zone, ready to take over.
Back up now queues an export with the engine's own backup client. Set a schedule from every hour to once a week. Each recovery point starts as Not tested. Test restore builds an isolated copy with its own volume and credentials, restores into it, and checks that an application can connect.
Run a digest-pinned image on your own Docker server or Kubernetes cluster, with retained storage and a separate application role that can't create databases or roles. Or create PostgreSQL 17 on RDS or Cloud SQL, review the compute, disk, access and backup settings, and approve only that.
Open source and self-hosted. Your applications don't need Forge, or Go.
docker pull ghcr.io/xraph/loomplane:latestServerbrew install xraph/tap/loomctlCLI