Open source
AGPL-3.0-or-later0free forever
- Identical features to the commercial edition
- No license checks, no gating, no remote control
- Deploy, modify and audit as you like
- Publishing it as a service requires sharing the corresponding source
AGPL-3.0-or-later · No license checks · Self-hosted
Open-source IDC billing & business system
Catalog, orders, billing, auto-provisioning, finance, tickets and resellers: seven stages sharing one dataset.
Laravel 12 + Vue 3 · three frontends · server-side pricing · auditable source
- 3apps
- Admin · storefront · client console
- 8domains
- Catalog, orders, finance, users and more
- 6plugins
- Upstream · payment · SMS · captcha · KYC · mail
- 0USD
- Free under AGPL, no feature gating
Revenue MTD¥ 86,420.00+12.4%
Open orders123 pending
Live instances318+26 this month
Revenue, last 7 daysMock
- #S-10231Plan A · monthlyActive
- #S-10232Plan B · yearlyProvisioning
- #S-10233Plan A · quarterlyRenew soon
Ecosystem Partners
No particular order
Live demo
Open the demo 25Yun
A production storefront running TuraIDC: catalog, checkout, payment and the client console, all live.
One backend for the entire IDC workflow
From publishing a product to closing the books, without a second spreadsheet.
Catalog & pricing
Multi-cycle pricing, configurable options, stock and reseller discounts; totals are always recomputed server-side.
Orders & provisioning
Checkout, payment callbacks, upstream provisioning, retries, suspend and release on expiry.
Finance
Balance, top-ups, invoices, refunds, reconciliation and ledger; amounts accumulated in cents.
Accounts
KYC, membership tiers, reseller commissions, payouts and login risk control.
Tickets
Department routing, auto-close on timeout, attachment protection, upstream forwarding.
Notifications
In-app, email and SMS with configurable templates and retries.
Automation
Scheduled jobs, heartbeat monitoring, reconciliation, log archiving.
Plugins
Six plugin families with clear boundaries: swap an upstream without touching the core.
One pipeline from checkout to reconciliation
Six stages share the same orders, accounts and ledger; a failed step rolls back, so you never see provisioned-but-unpaid.
- 01
Catalog
Groups, options, cycles, stock
- 02
Checkout
Quote token, server-side totals
- 03
Provisioning
Upstream plugins, automatic retry
- 04
Billing & renewal
Expiry notices, auto-renew, upgrades
- 05
Reconciliation
Ledger, refunds, invoices, MRR
- 06
Tickets & alerts
Auto-close, email and SMS
Start with the flaws we don't have
The issues commonly reported against commercial IDC systems, each mapped to an implementation you can verify in the repository.
We don't have7 issues avoided
Price tampering
Order and renewal totals are recomputed server-side; client parameters cannot rewrite the amount due.
Leaked upstream credentials
Upstream tokens stay server-side; clients and anonymous requests never receive the raw JWT.
Arbitrary file upload
Uploads require authentication and are validated for type, size and quota.
Feature gating and backdoors
No license checks, no disabled features, no remote control; the code is fully auditable.
Cross-tenant access
Queries and mutations bind to the current owner; violations return 403 / 404.
Payment replay
Idempotent callbacks plus a unique transaction constraint: each payment is booked and fulfilled once.
Injection and spoofing
Parameterized SQL; untrusted proxy headers ignored for client IP; secure cookies and CSRF protection.
We do have6 safeguards
Authoritative server-side math
Amounts, stock, coupons and renewals recomputed and locked server-side.
Complete audit trail
Money movements, orders and admin actions are recorded and exportable.
Login risk control
Soft lockouts per account and IP; captcha throttled per target.
Plugin architecture
Six plugin families with explicit boundaries, replaceable end to end.
Automated fallbacks
Scheduling, heartbeats, reconciliation, retries and automatic release.
Open and auditable
AGPL-3.0-or-later: review, patch and extend in the open.
Three deployment shapes
One codebase: Docker Compose, BaoTa panel or bare metal. Rewrite rules and cron setup ship in the docs.
- Fastest
Docker Compose
One compose file brings up the apps, MySQL and Redis; the host only runs containers.
Docker guide - Common
BaoTa panel
Four sites plus rewrite rules; PHP and cron managed inside the panel.
BaoTa guide - Explicit
Bare metal
Bring your own PHP-FPM, MySQL, Redis and Nginx; every request path stays visible.
Bare-metal guide
Move over from ZJMF Finance
Products, customers, orders, upstreams and KYC records migrate step by step; both systems can talk to each other during the switch.
Migration guide- 01Whole-database migration with checklists before and after
- 02A ZJMF compatibility plugin lets the legacy system call TuraIDC as an upstream
- 03ZJMF can also be attached as a supplier
Free to self-host, paid only to close the source
Both editions are feature-identical: stay open and pay nothing, or buy a license to keep your fork closed. No per-instance or per-order tax.
Commercial
Optional path for closed source¥200CNY · per year
- For closed distribution or when AGPL source duties don't fit
- Unlocks no extra features
- Suited to teams with a compliance review
- Terms and attribution follow LICENSE-COMMERCIAL.md
Pricing and licensing mirror the repository README and LICENSE-COMMERCIAL.md; the files in the repository are authoritative.
What to confirm before going live
The six questions we hear most before launch.
Is it really free?
The open-source edition is free under AGPL-3.0-or-later, with no feature gating, no license checks and no backdoors. The full source is auditable.
Can I run it closed-source commercially?
That needs the commercial license (CNY 200 / year), which grants terms outside AGPL. Without it, offering the modified system as a service requires sharing the complete corresponding source, including your changes.
Can I migrate from ZJMF Finance?
Yes. Products, customers, orders, upstreams and KYC data have documented migration paths and checklists; TuraIDC can also act as an upstream so both systems run in parallel first.
Which upstreams and payment channels are supported?
Upstreams, payments, SMS, captcha, KYC and mail are all plugins. ZJMF, KangHostx and EPay ship built in; anything else follows the plugin contract without touching the core.
What server environment does it need?
PHP 8.3+ with Laravel 12, MySQL 5.7.8+ (8.0 recommended) and Redis 6+. The three frontends build to static assets served by Nginx. Sizing details are in the deployment docs.
Where do I start customizing?
Read the architecture and frontend guidelines first, then pick one business domain. Plugins live in backend/plugins/{domain}/{slug}/; do not add logic to system routes, schedules or global middleware.