Industry Solution
Enterprise Fixed-Asset SaaS Cloud vs. On-Premises Deployment — Parameters and Selection Guide
Enterprise fixed-asset management SaaS vs. on-premises deployment — core parameters: daily cloud backup, 99.5% availability, customer-owned private network, three-tier selection table and pricing, plus applicable scale and when it is not the right fit.
- { "Two deployment models": "SaaS cloud / customer-owned local server on a private network" }
- Cloud business data backed up daily, monthly availability target 99.5%
- Transparent three-tier pricing, no module-based or per-user add-on fees
When to choose cloud or on-premises for your corporate fixed-asset system
Before deploying a fixed-asset management system, the first question to answer is "can the asset data live in the cloud?" Companies that accept the cloud and have no dedicated IT ops staff go with SaaS cloud, choosing the Basic or Pro plan by asset scale; companies that must keep data fully in-house / deploy on an internal network / meet regulatory compliance requirements go with the on-premises edition (customer-owned local server, private network).
Applicable profile:
- 100–5000 fixed assets (computers, servers, office equipment, lab equipment, vehicles, etc.) that need a unified ledger
- Cross-department, multi-floor / multi-site asset ownership and location that must be managed hierarchically
- The cloud vs. local trade-off comes down to "security" and "deployment cost"
- Currently weighing whether an annual SaaS fee or a one-time buyout is more economical
Core parameter table
| Parameter | Metric | Status |
|---|---|---|
| Deployment model | SaaS cloud / customer-owned local server · private network | ✅ Shipped |
| Cloud data backup | Daily backup of business data | ✅ Shipped |
| Cloud availability | Monthly availability target 99.5% | ✅ Shipped |
| On-premises deployment | One-click Docker install, customer self-deploys, no implementation fee | ✅ Shipped |
| Permission & approval governance | Role-based permissions / multi-level approval / cross-department countersign / fully auditable | ✅ Shipped |
| Location node governance | Site → Building → Floor → Office area → Room, multi-level | ✅ Shipped |
| Full asset lifecycle | In-use / idle / repair / retired four states + timeline + approval trail | ✅ Shipped |
| ERP integration | Standard REST API + CSV import/export | ✅ Shipped |
| MES real-time two-way integration | Pull routing / push process progress / exception callbacks | 🛣️ In exploration |
Cloud and on-premises share the same feature set (asset ledger, counts, permissions, approvals, reports) — the choice only affects "where data lives and who maintains it," not the feature set.
How to choose cloud vs. on-premises: one table
| Decision factor | Choose SaaS cloud | Choose on-premises edition |
|---|---|---|
| Where data lives | Platform-hosted, daily business data backup | Customer-owned server / private network |
| Who maintains it | Platform handles backup, availability, upgrades | Customer self-maintains; buyout price includes 6 months of standard warranty |
| Investment model | Annual fee (CNY 2999 / CNY 5999 per year) | One-time buyout (CNY 9999) + server and ops costs |
| Best fit for | Cloud-accepting companies with no dedicated IT ops | Companies that need data in-house / intranet / regulatory compliance and have IT staff |
| Startup cost | Low — pay annually after a 14-day trial | No implementation fee, but you must provide your own server environment |
The core decision is just one: can the asset data live in the cloud, and does the company have anyone to manage the servers? If data can live in the cloud and nobody manages the servers, stop hesitating — go SaaS; only when data must stay in-house or regulations explicitly require it does on-premises deployment come into play.
Coverage: applicable scale
| Scale | Plan | Notes |
|---|---|---|
| Up to 1000 assets | SaaS Basic | CNY 2999/year, small-scale starter |
| 1000–5000 assets | SaaS Pro | CNY 5999/year, recommended tier |
| Unlimited assets / in-house data | On-premises edition | CNY 9999 permanent buyout, no implementation fee |
All three official editions are unlimited-user — no module-based or per-user add-on fees. Hardware: SEUIC AUTOID UTouch handheld (UHF RFID), no more than CNY 4,000 per unit (subject to the purchasing quote); TSC TTP-244 Pro label printer. Software can be purchased standalone and is not bundled with hardware.
When it is not the right fit
- Ledger and physical items don't match: do a full count and align the baseline before going live. RFID prevents "can't find it from now on," it doesn't recover what is already lost. The baseline checklist in Factory Shop Floor RFID Prerequisites applies here too.
- Only a few dozen assets and simple requirements: Excel is enough — the ROI on tagging plus a handheld doesn't justify it.
- Insisting on on-premises with no IT staff: on-premises means providing your own server, maintaining and upgrading it yourself; without the ops capability it ends up being more of a hassle.
- Need real-time two-way MES integration: that is on the roadmap (🛣️ in exploration); current delivery is standard REST API + CSV, so don't treat automatic integration as a shipped capability.
- Hard requirements on cloud SLA / compliance: specific terms are governed by the contract — confirm written commitments with sales before purchase.
Corresponding models and plans
| Item | Spec | Cost |
|---|---|---|
| SaaS Basic | 1000 assets, unlimited users | CNY 2999/year |
| SaaS Pro | 5000 assets, unlimited users | CNY 5999/year |
| On-premises edition | Unlimited assets, permanent buyout, no implementation fee | CNY 9999 |
| Handheld | SEUIC AUTOID UTouch (UHF RFID) | Hardware no more than CNY 4,000 (subject to purchasing quote) |
| Label printer | TSC TTP-244 Pro thermal transfer | Subject to purchasing quote |
Most companies with 100–5000 fixed assets that accept the cloud land on the Pro plan; consider the on-premises edition only when data must be fully self-held or assets exceed 5000. For a finer-grained total-cost comparison, see RFID Asset Management System Pricing and TCO Comparison.
Rollout in three steps: ① Count existing assets and build one-tag-per-item records (batch import from the registration template); ② assign permissions and approval flows by department, then tag and register; ③ activate the handheld and plan, run one monthly full count and one cross-department transfer, and get ledger-vs-physical variance data within two weeks.
FAQ
Q: Is it safe to keep asset data in the cloud?
A: AssetaGuard cloud business data is backed up daily with a 99.5% monthly availability target, and permission and approval governance is shipped (✅) — each department only sees assets within its permissions. If data must be fully in-house or regulations mandate local storage, choose the on-premises edition directly. Specific SLA and compliance terms are governed by the contract.
Q: Is the on-premises edition hard to deploy?
A: One-click Docker install, no implementation fee — customers self-deploy on their own server and private network. Compared with SaaS, you need to provide the server environment and maintain and upgrade it yourself (the buyout price includes 6 months of standard warranty; follow-on support and upgrades are billed separately per quote). It suits companies with IT staff; don't force on-premises without the ops capability.
Q: If we start on the cloud, can we migrate back on-premises later?
A: Data can be exported via standard REST API and CSV import/export, so the ledger-physical baseline moves with you. For a complete cross-deployment migration path, confirm migration and implementation arrangements with sales before purchase; migration cost is billed separately based on the actual environment.
Pricing inquiry and next steps
If you have 100–5000 fixed assets, are weighing SaaS against on-premises, and need the parameter table, three-tier quotes, or a deployment-model comparison, get the enterprise fixed-asset SaaS and on-premises plan and quote.