FURAZHIR / deployment topology

The panel runs in your environment.
No mandatory external control plane.

FURAZHIR’s base production model is a separate single-tenant installation. Web, one-shot migrations, and worker roles are separated, PostgreSQL remains the source of truth, and infrastructure keys belong to the customer.

Open demo Try the demo panel

01separate runtime roles: 3
02production source of truth: PostgreSQL
03reproducible delivery: Docker
04mandatory external control planes: 0

01 / TOPOLOGY

Separated roles instead of one fragile container

Components ship as one version but run according to purpose. This simplifies migrations, worker scaling, and readiness diagnosis.

01request path

Web

Serves Studio, the public API, and health endpoints. It does not run schema migrations on every start or replace a dedicated background worker.

02migration check

Migrations

A one-shot role applies immutable SQL migrations before web and worker are updated. Migration state can be checked without applying changes.

03async runtime

Worker

Acquires leases and processes outbox, retries, and retention. A heartbeat distinguishes a live HTTP process from a functioning background runtime.

02 / INFRASTRUCTURE

What the installation needs

FURAZHIR does not hide database, files, or email in its own SaaS. You choose providers and own their region, access, resilience, and contracts.

01required

PostgreSQL with TLS

A separate database per deployment, constrained application and migration roles, private networking, and a verifiable backup policy.

02optional

S3-compatible media

Optional private object storage with lifecycle controls and dedicated credentials; objects are not made public by default.

03customer keys

SMTP and external APIs

Transport TLS verification and provider keys are configured in the customer environment. Outbound effects pass through an observable outbox.

03 / RELEASE ORDER

Deployment ends with acceptance, not docker compose up

A running container is only the first signal. Production is ready after migrations, readiness, heartbeat, a restore exercise, and a documented rollback.

01bootstrap

Bootstrap and secrets

Admin token, TOTP, and API key are generated; existing configuration is not silently overwritten, and secrets never enter Git or the image.

02verify

Service checks

Liveness covers the process, readiness covers dependencies, and worker heartbeat covers background work; PostgreSQL, S3, and SMTP are probed separately.

03recover

Backup, restore, and rollback

Before traffic, create a backup, exercise restoration, and retain the previous release for controlled rollback.

04 / HOSTING OPTIONS

One architecture, different infrastructure choices

FURAZHIR does not promise the same SLA across providers. The choice depends on team maturity, data region, network constraints, and willingness to operate PostgreSQL.

Option	Good fit	Verify
Cloud VM + Compose	Fast single-node launch	Backups, private network, disk alerts
Managed PostgreSQL	Less manual database work	TLS, region, restore, roles, cost
Own cluster	A mature platform team exists	Ingress, secrets, jobs, storage, probes
On-premise	An internal perimeter is mandatory	Updates, registry, monitoring, DR
Timeweb Cloud	Infrastructure is needed in a chosen Russian region	Actual region of every resource and Compose constraints

WORKING DATA

Every product receives a separate database

The working installation uses PostgreSQL in the customer-selected environment. The demo is only for evaluating the interface and never shares customer data.

01
Every buyer receives a separate installation, database, and keys.
02
Backup and restoration are exercised before a live launch.
03
Storage location is verified for every created resource.

05 / ANSWERS

Questions about this topic

01Can FURAZHIR run locally in Docker?

Yes. The package uses Docker and Compose for reproducible startup. Production additionally requires secrets, PostgreSQL, backups, TLS, and observability to be configured.

02Must FURAZHIR connect to the developer’s cloud?

No mandatory external control plane handles the workload. External services appear only when SMTP, S3, a payment provider, or another integration is connected.

03Is storing data on a server in Russia sufficient for compliance?

No. Location is only one requirement. Legal grounds, documents, notices, protection measures, retention, contracts, and verified operations are also needed.

06 / RELATED GUIDES

SecuritySecurity model for self-hosted FURAZHIR: single-tenant isolation, TOTP, server sessions, CSRF/CORS, audit, rate limits, and webhook verification.

Backend APIFURAZHIR API: 7 public v1 operations, OpenAPI 3.1, TypeScript SDK, scopes, rate limits, idempotency, worker/outbox, and 54 internal Studio server routes.

PricingCore at 29,900 RUB, Agency for customer portfolios, and Enterprise for complex environments. Discuss requirements, schedule, and terms before work begins.

PLAN THE ENVIRONMENT