knative
Are you using Knative?
Are you using Knative?
If you are using Knative, we would love to know!
Why?
Tracking usage in OSS is hard, if you leave a comment on this issue we can better understand who our users are and deliver a better experience for YOU!
- We'd like to give your organization the opportunity to collaborate more closely with contributors (if you want to)
- We want to help promote your organization
- We want to show off all the awesome stuff our users are doing
How you can help
Submit a comment in this issue to include the following information, which would then also get included in the ADOPTERS.md file and (if applicable) on the Knative homepage:
Organization/Company:
Website:
Country:
Contact: (email or Twitter at least one please!)
Usage scenario: e.g. We use Knative for XYZ
Status: Development?/Production?
Organization/Company: IBM
Project/Product Name: IBM Cloud Code Engine
Website: https://cloud.ibm.com/codeengine
Country: USA
Contact: @IBMCodeEngine
Usage scenario: Code Engine is a managed cloud-based hosting service. We host containerized workloads and for web-serving ones we use Knative Serving as the infrastructure. We are also using Knative Eventing as the basis for our eventing support.
Status: Production
Organization/Company: VMware Project/Product Name: Cloud Native Runtimes for VMware Tanzu Website: https://network.tanzu.vmware.com/products/serverless Country: USA Contact: [email protected] Usage scenario: Cloud Native Runtimes for VMware Tanzu is a application runtime for Kubernetes based on the OSS project Knative and represents the serverless capabilities in VMware Tanzu Advanced edition. It can be installed on any conformant K8s distribution in the public or private cloud. Status: Generally Available
Organization/Company: VMware Project/Product Name: VMware Event Broker Appliance (VEBA) Website: https://vmweventbroker.io/ Country: USA Contact: [email protected] Usage scenario: VEBA's core is based on Knative Serving and Eventing to deliver a simplified FaaS and serverless experience for users with little to no software development background. VEBA is released as an open source Fling and not intended for production use. Status: Development
Organization/Company: Blue Origin Website: https://www.blueorigin.com/ Country: USA Contact: @tomabeles Usage scenario: We use several Knative workloads as synchronization services between various third-party and in-house applications. Some of these are run on a schedule basis, others due to a change in one or more systems. Status: Production
Organization/Company: TriggerMesh Website: https://triggermesh.com Country: USA Contact: @TriggerMesh Usage scenario: Built on Knative, the TriggerMesh integration platform connects data and events from virtually any application or platform to any other, in the cloud or on-premises. Status: Production
Organization/Company: Tata Communications Website: https://www.tatacommunications.com/solutions/cloud/platforms/ Country: India Contact: @Shashankft9 Usage scenario: We are using knative serving and eventing to provide a FaaS and serverless experience for end users. We are using it internally to run on-demand containers for remedies and other event driven use-cases. Status: Development
Organization/Company: Red Hat Project/Product Name: Red Hat OpenShift Serverless Website: https://www.openshift.com/learn/topics/serverless Country: USA Contact: @openshift Usage scenario: Containerized workloads and functions are being deployed as Knative Serving. We are also using Knative Eventing as the basis for our eventing support. Available everywhere OpenShift is. Status: Generally Available
Organization/Company: Grey Rook Website: https://www.greyrook.com Country: Germany Contact: [email protected] Usage scenario: Serving and eventing are the base for our backend stack that we use to build awesome web- and mobile apps for our clients Status: Development & Production
Organization/Company: Scaleway Website: https://www.scaleway.com/en/ Country: France Contact: [email protected] Usage scenario: We use Knative Serving as the core of our Function as a Service and Container as a Service products. We aim to provide our customer the tools to easily deploy their application. Status: Public Beta
Organization/Company: deepc.ai
Website: https://www.deepc.ai/
Country: Germany
Contact: [email protected]
Usage scenario: Standardized across engineering teams Knative is the foundation upon which all products at deepc are built. Whether it be our server-less platform medial AI, our front-end based app or our hardware integrated edge deployments.
Status: Production
- Organization/Company: KubeSphere
- Website: https://kubesphere.io/
- Country: China
- Contact: (email or Twitter at least one please!) [email protected] / @FeynmanZhou
- Usage scenario: We use Knative for our Function as a Service product, see the OpenFunction project for more details.
- Status: Development & Production
Organization/Company: Liquidx Website: https://www.liquidx.com/ Country: USA Contact: [email protected] Usage scenario: We use Knative to power our InBlock product - Blockchain enabled physical goods trading operations orchestrator. Product modules cover Order Creation, Shipping, Invoice Management, Payment Reconciliation, an Cash Forecasting Status: Production
Organization/Company: Optum
Website: optum.com
Country: USA
Contact: [email protected]
Usage scenario: Knative serving/eventing is the base building block of our on-premises serverless platform, used by our developers to deploy event-driven workloads.
Status: Production
Organization/Company: EASE lab @ University of Edinbugh Website: https://easelab.inf.ed.ac.uk Country: UK Contact: https://github.com/ease-lab/vhive / [email protected] Usage scenario: e.g. We use Knative for XYZ Status: vHive is a full-stack open-source framework & ecosystem for serverless experimentation and innovation. vHive is representative of real serverless clouds, integrating production-grade components, including AWS Firecracker and gVisor, Containerd and Kubernetes.
Organization/Company: vorteil pty ltd Website: https://github.com/vorteil/direktiv / http://vorteil.io Country: USA / Australia Contact: [email protected] Usage scenario: Serverless orchestration engine Status: Development & Production
Organization/Company: Spider.com Website: https://www.spider.com Country: USA Contact: [email protected] Usage scenario: We use Knative as a base for our APIs and data mining operations. Status: Development
Organization/Company: Google Cloud Website: https://cloud.google.com/anthos/run Country: USA Contact: [email protected] Usage scenario: Integrated with Anthos, Cloud Run for Anthos provides a flexible serverless development platform for hybrid and multicloud environments. Cloud Run for Anthos is Google's managed and fully supported Knative offering. Status: Production/Generally Available
Organization/Company: Alibaba Cloud Website: https://cs.console.aliyun.com Country: CHN Contact: [email protected] Usage scenario: Knative on Alibaba Cloud is deeply integrated with Alibaba Cloud products based on the Knative for the community to provide the purest experience of containerized Serverless. Status: Production
Organization/Company: Chainguard Website: https://chainguard.dev Country: USA Contact: [email protected] Usage scenario: Most of our platform is built on top of Knative wherever possible. We use both Serving / Eventing. Status: Development?/Production? Development
Organization/Company: SAP Project/Product Name: SAP Event Mesh Website: https://help.sap.com/viewer/product/SAP_EM/Cloud/en-US Country: Germany Contact: Technical: [email protected], Product Management: [email protected], Knative: [email protected] Usage scenario: SAP Event Mesh is a fully managed cloud service that allows applications to communicate through asynchronous CloudEvent standard events. Create responsive applications that are decoupled from the publisher to deliver event-driven business processes across your business ecosystem for greater agility and scalability. The Event Mesh utilizes Knative Eventing, specifically the "distributed" KafkaChannel which we sponsor. Status: Production
Organization/Company: Blue Origin Website: https://www.blueorigin.com/ Country: USA Contact: @BlueOrigin Usage scenario: We use several Knative workloads as synchronization services between various third-party and in-house applications. Some of these are run on a schedule basis, others due to a change in one or more systems. Status: Production
I now realize why I've been getting unsolicited emails from Github about this Issue for the past half a year, despite having no clue what Knative is. My account is named BlueOrigin, with no intention to impersonate a certain high profile billionaire's rocket company. Github uses the '@' tag to 'Mention' other Github accounts and this comment used my username by accident, probably as a Twitter handle?
I now realize why I've been getting unsolicited emails from Github about this Issue for the past half a year, despite having no clue what Knative is. My account is named BlueOrigin, with no intention to impersonate a certain high profile billionaire's rocket company. Github uses the '@' tag to 'Mention' other Github accounts and this comment used my username by accident, probably as a Twitter handle?
Sorry about that BlueOrigin I edited the comment
@BlueOrigin since you're still mentioned from this interaction even with the original comment edited, you might also want to click "unsubscribe" on the sidebar manually :)
Organization/Company: HighCohesion Website: https://www.highcohesion.com/ Country: UK Contact: Technical Lead: [email protected], Operations Director: [email protected], Usage scenario: SaaS platform to connect any ecommerce platform with any other, automating the data flow between them, in real time. Status: Development?/Production? Development
Organization/Company: ManoMano Website: https://www.manomano.es/ Country: Spain Contact: https://twitter.com/ManoMano_Tech Usage scenario: We use Knative Serving in production on AWS in top of EKS, in order to keep the cost of the cloud lower as possible for our web services apps, we really aim to pay for what we really need and avoid paying for idle resources. Currently we're industrializing Eventing for S3 event processing in our non-productions environments, and it'll be available in our production environments shortly. Status: Production(Serving)/Development(Eventing)
Organization/Company: ZITADEL Website: https://zitadel.com Country: Switzerland Contact: [email protected] @zitadel Usage scenario: We use Knative (most of the times Google Cloud Run) as a platform to run our serverless authentication and access solution called ZITADEL. Using Knative or one of its managed services offerings helps people to run a highly scalable login without the need for complex operations. Status: Production
Organization/Company: Blue Origin Website: https://www.blueorigin.com/ Country: USA Contact: @BlueOrigin Usage scenario: We use several Knative workloads as synchronization services between various third-party and in-house applications. Some of these are run on a schedule basis, others due to a change in one or more systems. Status: Production
I now realize why I've been getting unsolicited emails from Github about this Issue for the past half a year, despite having no clue what Knative is. My account is named BlueOrigin, with no intention to impersonate a certain high profile billionaire's rocket company. Github uses the '@' tag to 'Mention' other Github accounts and this comment used my username by accident, probably as a Twitter handle?
A certain high profile billionaire's rocket company has recently contacted me and wishes to commandeer my account name, to which I will soon acquiesce. Thus, if the original comment wanted to revert the "@" to how it was originally, it is now likely appropriate to do so :)
Organization/Company: SAP Project/Product Name: SAP Event Mesh Website: https://help.sap.com/viewer/product/SAP_EM/Cloud/en-US Country: Germany Contact: Technical: [email protected], Product Management: [email protected], Knative: [email protected] Usage scenario: SAP Event Mesh is a fully managed cloud service that allows applications to communicate through asynchronous CloudEvent standard events. Create responsive applications that are decoupled from the publisher to deliver event-driven business processes across your business ecosystem for greater agility and scalability. The Event Mesh utilizes Knative Eventing, specifically the "distributed" KafkaChannel which we sponsor. Status: Production
^ The above entry from Nov 18, 2021 should be removed as this project at SAP is no longer based on Knative Eventing. I have created PR to update the ADOPTERS.md file... https://github.com/knative/community/pull/1146 Thanks ; )
Organization/Company: Adobe Website: https://adobe.com/ Country: USA Contact: https://twitter.com/adobedevs Usage scenario: Adobe has several FaaS services on AWS, Azure & GCP. Adobe's Internal Developer Platform team is offering KNative as an alternative to vendor offerings. This is being offered on an Experimental basis. Status: Development
Organization/Company: KA-NABELL Website: https://www.ka-nabell.com Country: Japan Contact: [email protected] @kahirokunn Usage scenario: Largest trading card E-commerce in Japan Status: Development
