Beta
Choose hosted or self-hosted Mobazha
Choose the operating model from control, responsibility, integrations, and service needs—not from a false free-versus-paid shortcut.
Hosted service
Use the hosted application when you want to evaluate Mobazha or operate a store without maintaining the underlying server. The service operator manages availability, deployment, and the hosted account boundary; current Beta pricing and limits are published separately.
- Fastest path to the current buyer and seller experience.
- Service availability, data handling, limits, and future pricing depend on the hosted terms.
- Runtime capabilities still determine which commerce and payment paths are available.
Self-hosted node
Use the open-source Node when you need direct control over deployment, store data, domain, availability, backup, and enabled integrations. You operate the machine and remain responsible for security, recovery, upgrades, and third-party costs.
- No mandatory central Mobazha transaction fee is created merely by running the software.
- The current v0.3 line is a release candidate intended for evaluation and testnet use.
- BTC, BCH, and LTC are enabled by the default release boundary, subject to runtime and seller configuration.
Decision rule
- Choose hosted when reducing operational work matters more than controlling every infrastructure boundary.
- Choose self-hosted when control, portability, custom operation, or independent availability justifies the operating responsibility.
- Start on testnet and validate backup, payment, fulfillment, and recovery before depending on either path for material transactions.
- Re-evaluate from current terms and capabilities; the deployment choice does not permanently lock the product model.