ThingLogix Foundry pricing model has evolved from the normal fixed annual subscription price to usage-based model. The new model allows companies to experience greater flexibility in terms of aligning costs with actual usage volume as they develop, test, deploy, scale, and evolve their smart, connected solutions on Foundry and AWS core infrastructure. A key element of the new pricing structure is a free tier, which allows companies just getting started with IoT, or companies seeking to compartmentalize their development and test efforts for new IoT solutions, freedom to conduct initial proof-of-concept testing without incurring platform usage charges. As they evolve their solutions from laboratory concepts in test environments to robust, market-facing solutions in deployed environments, they incur charges commensurate with the volume of events that their deployed solutions are generating. Pricing is denominated in micro-cents per event, metered on a monthly basis. More specifically once the company transitions from the free-tier platform they have the flexibility to choose between two billing methods; Metered Usage and Object Pricing.

Metered Usage

ThingLogix charges based on the number of invocations of Foundry lambda functions. Companies will either use our default pricing grid or a custom grid depending on our business arrangement. The billing system in place has a contract component that carries the billing grid for each company. It also allows overrides and one time adjustments.

Object Pricing

In this scenario, ThingLogix charges a company a set rate for a number of a specific object type(s) in their Foundry instance. This is also set in a contract. Typically these are what we call "Active Assets" or assets that have an MQTT topic that actually talk to Foundry. In most cases, we charge a set fee that is initiated on the provisioning of that object. In some cases, it's a monthly fee in others it's a one time charge.