2Smart Core Pricing
Subscription license OPEX-based
A usage-based model where the monthly license fee scales with the number of devices.
Monthly fee include:
Perpetual license CAPEX-based
A one-time licensing model where you pay for implementation and receive source code.
Monthly fee include:
Hybrid license OPEX-to-CAPEX
A model that starts as a subscription with a predefined option to buy out the codebase.
The engagement begins with a one-time project phase covering custom development, white-labeling, deployment, and launch.
After go-live, the software is operated under a monthly fee for a defined period, covering platform usage, managed cloud infrastructure, and ongoing support.
Once the solution and business model are validated, you may acquire a one-time software license.
After the buyout, recurring payments are limited to managed infrastructure and optional support services.
License cost is determined by the 2Smart framework configuration included in the final solution
Device connectivity and integration
Device and asset management
Device firmware management
Data visualization
System reliability and maintenance
Automation and alarms
Mobile application
Business management and multitenancy
Extensibility and integrations
Comparison of cooperation models
Subscription license
Perpetual license
Hybrid license
Time-to-value
Fastest start
Fast, with a longer preparation phase
Fast, with a longer preparation phase
Commercial model
Low CAPEX / higher monthly OPEX
Higher upfront CAPEX (one-off) / low OPEX
Combined: OPEX first, then one-off
Software support
Included in the monthly fee
Additional SLA
Included until buyout, after buyout same as perpetual
Additional development
Time & Materials (hourly)
Time & Materials (hourly)
Time & Materials (hourly)
IP rights
Not transferred
Non-exclusive (exclusivity possible by agreement)
Not transferred before buyout, non-exclusive after buyout
Source code
Not provided
Full source code
Not provided before buyout, provided after buyout
Vendor lock-in
High
Low
Medium
Cost scalability
Scales with devices (license) and devices/data operations (infrastructure)
License is fixed; ongoing costs scale with devices/data operations
Before buyout: users + devices/data; after buyout: devices/data only
Exit options
Migration is more complex
Full freedom
Gradual
Managed private cloud FAQs
What is a managed private cloud?
A managed private cloud is a dedicated cloud environment provisioned exclusively for your solution and operated by our team. It provides isolated compute, storage, and networking resources, while we take full responsibility for availability, security, maintenance, and operational management under an SLA.
What does the managed infrastructure fee include?
It covers the ongoing operation and maintenance of your private cloud environment. This includes hosting, compute and storage resources, networking, monitoring, backups, security patching, availability management, incident response, and day-to-day DevOps operations. The fee scales with the number of connected devices and data operations.
Are there minimum fees or commitments?
Subscription-based models typically include a minimum monthly fee, even at low usage levels. Exact thresholds and commitments are defined in the commercial agreement.
Does infrastructure scaling affect the software license price?
No. Infrastructure scaling applies only to managed cloud costs.
Software license pricing is defined separately and depends on the selected licensing model (subscription, perpetual, or hybrid).
What is included in software support and updates?
Bug fixes, minor improvements, security updates, and technical assistance related to the platform. The exact scope and response times are defined by the applicable SLA.
Is software support included by default?
- Subscription license: Software support and updates are included in the monthly fee.
- Perpetual license: Software support and updates are included in the monthly fee, but provided under a separate SLA.
- Hybrid license: Software support is included during the subscription phase and requires separate SLA after the license buyout.
What does custom development and extensions mean?
Custom development covers all work beyond the standard 2Smart framework modules and typically starts with a discovery and domain alignment phase. During this phase, we analyse your business model, workflows, and technical requirements to design a solution tailored specifically to your use case.
Depending on the scope, we may craft a fully custom-grade solution, extending existing modules or introducing new architectural components and deep backend functionality where required. In some cases, no additional development is needed, and the solution can be delivered through customization of existing 2Smart modules only.
User interfaces are typically custom-designed to match your product branding, user roles, and operational workflows.
Custom development is delivered on a Time & Materials basis. In perpetual licensing models, this phase may be more extensive, as the solution is prepared for long-term ownership and independent operation.
What is included in software deployment and environment setup?
This covers deploying the solution to the target environment, configuring cloud resources, setting up access controls, security policies, networking, and preparing the platform for production use.
What does white-labeling include?
White-labeling means delivering the platform under your brand. This includes branding of the web platform interface and mobile applications, domain configuration, visual identity adjustments, and customization of user-facing elements.
What is included in testing, optimisation, and launch?
This phase includes functional testing, performance and load testing, security checks, optimisation of data pipelines, and final preparation for production launch to ensure stability and scalability.
What are non-exclusive IP rights?
Non-exclusive IP rights mean that you obtain the right to use, modify, and operate the software and its source code for your business purposes, while the vendor retains the right to reuse the underlying technology, components, and know-how in other projects and products.
What does source code transfer mean?
You receive the full source code of the delivered solution, including custom-developed components and agreed parts of the platform codebase, enabling independent hosting, maintenance, and further development.
Can we move to a self-managed environment later?
Yes. Depending on the licensing model and contractual terms, clients may migrate from managed cloud to a self-managed environment, particularly after acquiring a perpetual license or completing a buyout.
How does 2Smart Core support system reliability and maintenance?
2Smart Core includes a dedicated software module designed to maintain system reliability, availability, and overall operational stability.
The module provides built-in capabilities for monitoring, diagnostics, and recovery, including continuous system monitoring and error logging, automated backups and database rotation, configurable retention and recovery policies, uptime and performance dashboards, as well as health checks with proactive alerts for potential issues.
For businesses with higher availability requirements, the platform can be deployed with redundancy, failover mechanisms, and load balancing. These capabilities are enabled through infrastructure-level architecture decisions and may increase infrastructure costs, therefore, they are implemented based on the specific availability, scale, and resilience requirements of each business.
In self-managed environments, the platform’s operational tools integrate with and support the client’s own operational processes and infrastructure tooling.
Unique IoT needs have one real answer.
2Smart Core delivers custom-quality solutions under your ownership – fast, affordable, and backed by a battle-tested framework that embodies proven expertise.
Subscription license OPEX-based
A usage-based model where the monthly license fee scales with the number of devices.
Monthly fee include:
-
Software usage without transfer of IP rights and without access to source code
-
Software updates and basic technical support
One-time payment:
-
Custom development and extensions
-
Software deployment and environment setup (optional, on client infrastructure)
-
White-labeling
-
Testing, optimisation, launch
-
Client team onboarding and training
Perpetual license CAPEX-based
A one-time licensing model where you pay for implementation and receive source code.
Monthly fee include (optional):
-
Software support and updates (additional SLA)
One-time payment:
-
Software license buyout (non-exclusive IP rights and source code transfer)
-
Custom development and extensions
-
Software deployment and environment setup (optional, on client infrastructure)
-
White-labeling
-
Testing, optimisation, launch
-
Client team onboarding and training
Hybrid license OPEX-to-CAPEX
A model that starts as a subscription with a predefined option to buy out the codebase.
The engagement starts with a one-time project phase covering custom development, white-labeling, deployment on your infrastructure, and launch.
After go-live, the solution operates under a subscription-based license for a defined period (typically six months or longer). During this phase, you pay a monthly license fee for platform usage. Infrastructure is fully self-managed.
Once the solution and business model are validated, you may acquire a one-time software license. After the buyout, recurring payments are limited to optional software support and updates under a separate SLA.
License cost is determined by the 2Smart framework configuration included in the final solution
Device connectivity and integration
Device and asset management
Device firmware management
Data visualization
System reliability and maintenance
Automation and alarms
Mobile application
Business management and multitenancy
Extensibility and integrations
Comparison of cooperation models
Subscription license
Perpetual license
Hybrid license
Time-to-value
Fastest start
Fast, with a longer preparation phase
Fast, with a longer preparation phase
CAPEX / OPEX
Low CAPEX / higher monthly OPEX
Higher upfront CAPEX (one-off) / internal OPEX
Combined: OPEX first, then one-off
Software support
Included in the monthly fee
Additional SLA
Included until buyout, after buyout same as perpetual
Additional development
Time & Materials (hourly)
Time & Materials (hourly)
Time & Materials (hourly)
IP rights
Not transferred
Non-exclusive (exclusivity possible by agreement)
Not transferred before buyout, non-exclusive after buyout
Source code
Not provided
Full source code
Not provided before buyout, provided after buyout
Vendor lock-in
High
Low
Medium
Cost scalability
License costs scale with devices; infrastructure costs depend on your environment, devices, and data operations
License is fixed; ongoing costs depend on your infrastructure, devices, and data operations
Before buyout: license scales with users; after buyout: only infrastructure costs (devices/data)
Infrastructure
Fully self-managed by the client
Fully self-managed by the client
Fully self-managed by the client
Exit options
Full freedom
Full freedom
Full freedom
Self-managed infrastructure FAQs
What does self-managed deployment mean?
Self-managed deployment means that the platform is deployed and operated within your own infrastructure, which can be either on-premises or in your preferred cloud environment (public or private).
You are responsible for infrastructure provisioning, operations, security, scaling, and availability, while we provide the software, documentation, and optional support services.
Can self-managed deployment run in the cloud?
Yes. A self-managed deployment can run in any cloud environment you control, including AWS, Azure, Google Cloud. “Self-managed” refers to operational responsibility, not to the physical location of the infrastructure.
Do you support on-premises deployments?
Yes. The platform can be deployed in on-premises environments, including private data centres, industrial networks, or restricted environments with limited connectivity, subject to technical requirements defined during discovery.
What is included by default in a self-managed model?
- Software licensing according to the selected license model
- Full technical documentation
- Deployment guidelines and architecture recommendations
- Release packages and update instructions
Infrastructure provisioning and operations are handled by the client.
Can you help with deployment on our infrastructure?
Yes. Deployment assistance is available as an optional service.
We can support or perform the initial deployment in your on-premises or cloud environment, validate the setup, and hand over operational control to your team.
Is ongoing infrastructure support included in self-managed models?
No. Ongoing infrastructure operations are not included in self-managed models.
However, software support and updates may be included (subscription) or provided under a separate SLA (perpetual and post-buyout hybrid).
When does a self-managed model make the most sense?
- Require full control over infrastructure and security
- Already operate cloud or on-prem platforms
- Need to comply with internal IT or regulatory constraints
- Plan long-term independent operation after license buyout
Can we move from a self-managed deployment to a managed private cloud?
Yes. It is possible to transition from a self-managed deployment to our managed private cloud.
Such a transition is handled as a planned migration and typically includes environment assessment, data and configuration transfer, validation, and re-establishment of operational monitoring and SLAs.
Unique IoT needs have one real answer.
2Smart Core delivers custom-quality solutions under your ownership – fast, affordable, and backed by a battle-tested framework that embodies proven expertise.