SC

Confluent: sourced choices

21 product and go-to-market choices, oldest first. Back to the case study

  1. 2014Product · Commercial scope The founders established a company around enterprise data-in-motion infrastructure after creating Kafka. CF1
  2. 2015-01Product · Confluent Platform The company announced its first Platform release for customer-managed deployments. CF1
  3. 2017-11Product · Managed cloud Confluent Cloud became generally available as a managed service. CF1
  4. 2018-03Product · Stream processing The filing’s historical timeline dates general availability of ksqlDB to March 2018. CF1
  5. 2020-08Go_To_Market · Cloud marketplaces Confluent Cloud became available through the three leading cloud providers’ marketplaces. CF1
  6. 2021-06Product · Deployment choice Customers could use self-managed Platform or fully managed Cloud. CF1
  7. 2021-06Product · Connectors Prebuilt connectors linked streams with other applications and data systems. CF1
  8. 2021-06Product · Security and control Commercial functionality included role-based controls, audit logs and schema validation. CF1
  9. 2021-06Product · Cluster operations Platform features included self-balancing clusters, tiered storage and multi-region clusters. CF1
  10. 2021-06Product · Support Enterprise support and education accompanied production deployments. CF1
  11. 2021-06Product · Cloud operations Managed Cloud covered infrastructure operations, including scaling and maintenance. CF1
  12. 2021-06Go_To_Market · Developer entry Developers could learn and begin using the technology before a centrally negotiated purchase. CF1
  13. 2021-06Go_To_Market · Self-service The company offered a fully online learning and purchase route. CF1
  14. 2021-06Go_To_Market · Direct sales Experienced field teams served customers through a direct sales motion. CF1
  15. 2021-06Go_To_Market · Partner routes Systems integrators, software vendors and resellers supplemented direct selling. CF1
  16. 2021-06Go_To_Market · Platform charging Platform subscriptions were generally annual and priced per software instance. CF1
  17. 2021-06Go_To_Market · Cloud charging Cloud offered pay-as-you-go and usage-based minimum commitments. CF1
  18. 2021-06Go_To_Market · Committed usage Minimum-commitment Cloud contracts generally lasted at least one year. CF1
  19. 2021-06Go_To_Market · Community education Meetups, technical content and training supported the developer community. CF1
  20. 2021-06Go_To_Market · Account expansion The company pursued more use cases and larger workloads inside existing accounts. CF1
  21. 2021-06Go_To_Market · Professional services Implementation and education services supported adoption alongside subscriptions. CF1