Skip to content
Back to the index

cri-o

cri-o.ioInfrastructure

No liveness check has reached it yet; it is registered on GitHub and has been in the index since 9 Oct 2026. How this is checked

CRI-O is an open-source container runtime that implements the Kubernetes Container Runtime Interface using OCI-compliant images and containers. It is installed on Linux hosts and used by cluster operators with Kubernetes distributions and tools such as Minikube and kubeadm.

Inferred · not functionally tested

Open SourceApache-2.0WebLinuxSelf-hostedCLI
cri-o preview
Visit cri-o.io
5.7kstars
1.2kforks
7features
2016since

Overview

6 features

Purpose: Running OCI-compliant containers in Kubernetes without a heavyweight container runtime.

Inferred · not functionally tested

Audience: Kubernetes administrators and platform engineers

Inferred · not functionally tested

Functions: Unknown

Interfaces: API: unknown · MCP: unknown · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: Apache-2.0 · platforms: WEB · deployment: browser, linux, self_hosted, cli

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: cri-o.io · github.com. These links do not verify the individual claims.

cri-o is a Hosting, deployment & PaaS project. Inferred · not functionally tested: It focuses on running OCI-compliant containers in Kubernetes without a heavyweight container runtime. Inferred · not functionally tested: cri-o is an open-source project aimed at kubernetes administrators and platform engineers. Basis unknown · not verified: cri-o is open source under the Apache-2.0 license. Basis unknown · not verified: cri-o is available on the web, Linux, and the command line, and it can be self-hosted.

It is developed by CRI-O Project, and it first shipped in 2016. The project is developed in the open on GitHub with 5.7k stars and 213 commits in the last 90 days. Inferred · not functionally tested: Key capabilities include OCI image support, kubernetes integration, and registry support.

Summary written by a language model from the project’s public pages.

Tasks: Inferred · not functionally tested

  • OCI image support
  • Kubernetes integration
  • Registry support
  • Container execution
  • Minikube integration
  • kubeadm integration

Topics: Inferred · not functionally tested

Tags
oci-runtimekubernetes-runtimecontainer-enginelinux-containers

JSON profile · Text profile · Access guide

Built with & integrations

Written with
Claude Code
Runs on
BrowserLinuxSelf-hostedCLI
Written with — evidence
Claude Code
commit 9a62e5381231 · since Oct 2026

Trust & compliance

License
Apache-2.0
Public signals
HTTPSOpen SourceFree tierGitHub · ★ 5.7kActive maintenance

Indexing history

1

What PulseGate has recorded for this listing

  1. Indexed8 Oct · 21:39 UTC
    Cri O seen via Saashub
    Source: Saashub · Open

Frequently asked questions about cri-o

What is cri-o?
Inferred · not functionally tested: Cri-o focuses on running OCI-compliant containers in Kubernetes without a heavyweight container runtime. It is catalogued under Hosting, deployment & PaaS on PulseGate.
Who is cri-o for?
Inferred · not functionally tested: cri-o is an open-source project built for kubernetes administrators and platform engineers.
Is cri-o free?
Basis unknown · not verified: Yes — cri-o is open source under the Apache-2.0 license and free to use.
What platforms does cri-o run on?
Basis unknown · not verified: cri-o runs on the web, Linux, and the command line. It can also be self-hosted.
Is cri-o still maintained?
The GitHub repository shows 213 commits in the last 90 days.
What are alternatives to cri-o?
Similar projects tracked by PulseGate include ServerMO, Ship your site, and PPCDN.ServerMOShip your sitePPCDN
Who develops cri-o?
cri-o is developed by CRI-O Project.
When did cri-o launch?
cri-o first shipped in 2016.

Also in Hosting, deployment & PaaS

Same category — not a similarity match