Event Based Pricing Press Release

http://www.thinglogix.com/media/thinglogix-announces-event-based-pricing-for-internet-of-things-platform/


Default Event Based Pricing 



Lambda events per month

Tier

Min

Max

Cost per event ($)

Free tier

0

99,999

--

Tier 1

100,000

999,999

0.00005

Tier 2

1,000,000

999,999,999

0.0000425

Tier 3

1,000,000,000

2,499,000,000

0.00004

Mega-volume

2,500,000,000

10,000,000,000

0.0000375


Summary


ThingLogix defines an “event” as a single communications transmission from a deployed device or application to Foundry, or from Foundry to the deployed device or application (i.e. events can be bi-directional). Events in Foundry are synonymous with events as AWS defines them in the context of its Lambda compute service.


Event-based pricing for ThingLogix Foundry eliminates the traditional fixed annual subscription pricing model that ThingLogix has historically used and replaces it with a fully transparent pricing schema that scales with the needs of organizations developing and operating IoT solutions. The actual fee that a customer pays depends on the volume of events that the customer’s smart, connected solution generates through Foundry, and will vary each month commensurate with usage. In addition to the free pricing tier (i.e. unit price equals zero), ThingLogix has defined four additional pricing tiers that align with event volume. If customer usage volume exceeds the range that defines a pricing tier, then the unit pricing resets at a lower price as stipulated by the volume range for that next higher tier of event volume. ThingLogix has defined the event volume ranges to accommodate the volume that most enterprises are likely to experience with their deployed IoT solutions at this stage of the market’s evolution. If a customer’s usage volume routinely exceeds the range that defines the maximum level of the highest volume tier by a significant factor, ThingLogix may suggest a lower, customized unit price unique to that customer. 


Standard Assumptions

Our standard assumptions when estimating usage are as follows:

1 Message generates 3 Foundry Events