FURAZHIR / for agencies and integrators

Repeat the engineering foundation.
Do not repeat customer constraints.

FURAZHIR separates a stable operating foundation from project-specific domain logic. A Russian web agency or integrator with backend and DevOps can evaluate the working demo, discuss a customer project, and choose an Agency engagement for a portfolio of launches.

Open demo Read the documentation

01tokens and brand configuration: white-label
02separate customer deployment: 1:1
03transferable contract: OpenAPI
04clear project delivery: Docs

01 / REUSABLE FOUNDATION

What can be standardized across projects

The customer’s business is not standardized. The quality of the utility layer is: access, CRUD, audit, integrations, background work, and operational delivery.

01rebrand

Design tokens instead of copied CSS

Palette, typography, density, surfaces, and states form a theme system. Rebranding does not require changes to panel domain logic.

02clear delivery

Contracts instead of oral agreements

Public API v1, OpenAPI, and the TypeScript SDK give frontend, integration, and customer teams one verifiable surface.

03operations

Instructions instead of one developer’s memory

Initial setup, migrations, service checks, backup, restoration, and rollback are part of project delivery.

02 / CUSTOMER PROJECT

What remains unique every time

A ready foundation reduces repeated work but must not present integration and discovery as a one-click setting.

01discovery

Domain entities and processes

The team identifies sources of truth, lifecycles, action permissions, and critical transactions for the exact business.

02adapters

Integrations and migration

CRM, ERP, payments, SSO, legacy APIs, and data import use project adapters and separate acceptance.

03customer boundary

Threat model and legal environment

Data region, roles, retention, contracts, and industry requirements come from the system owner—not a universal template.

03 / CUSTOMER HANDOFF

A delivery that can be accepted and maintained

The customer must know what was received, how to run it, where data lives, and who can access it. Documentation and a walkthrough make the project maintainable.

01package contents

Versioned package

The agreement lists the source code or images, Docker Compose setup, migrations, SDK, and documentation included in delivery.

02isolation

Secure delivery

Keys are created for the specific customer and transferred separately. Data and access from other projects are never included.

03acceptance

Training and launch period

The customer team walks through primary flows, health, and recovery. Included support duration does not limit the delivered version’s usage term.

04 / ENGAGEMENT MODEL

Core and Agency serve different scales

Core serves one product, while Agency serves a customer-project portfolio under separate delivery terms.

Scenario	Core	Agency
One end product	Yes, one deployment	Also possible
Customer portfolio	No	Under a separate agreement
White-label	One project brand	Process for multiple brands
Third-party transfer	Only as stated by EULA	Defined separately
Support	30 launch days	Project-specific policy

NOT A ONE-BUILD FRANCHISE

Reuse must preserve isolation and responsibility

The Agency model does not turn customers into tenants of one hidden database. A safe approach uses a separate installation, secrets, data, and acceptance process for every product.

01
The customer package has an explicit, agreed contents list.
02
Keys, data, and backups stay separate for every project.
03
Modification and redistribution rights are fixed in the customer agreement.

05 / ANSWERS

Questions about this topic

01Can the FURAZHIR visual system be replaced completely?

Yes. The interface uses design tokens for themes and key states. A project rebrand still needs visual and accessibility acceptance.

02Does the customer receive source code?

The format may include source code or ready-to-run images. Exact contents, modification rights, and delivery terms are agreed before payment.

03Can one package cover an agency portfolio?

Agency is the option for a customer-project portfolio. The agreement defines the number of environments, modification and transfer rights, support, and installation accounting.

06 / RELATED GUIDES

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

Build vs buyA practical build-vs-buy comparison covering CRUD, access, audit, API, workers, integrations, operations, code ownership, and honest decision criteria.

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

EVALUATE AS AN AGENCY