The Runpod Hub is a centralized repository that enables users to discover, share, and deploy preconfigured AI repos optimized for Runpod’s Serverless infrastructure. It serves as a catalog of vetted, open-source repositories that can be deployed with minimal setup, creating a collaborative ecosystem for AI developers and users. Whether you’re a developer looking to share your work or a user seeking preconfigured solutions, the Hub makes discovering and deploying AI projects seamless and efficient.

​
Why use the Hub?

The Hub simplifies the entire lifecycle of repo sharing and deployment, from initial submission through testing, discovery, and usage.

​
For Runpod users

  • Find production-ready AI solutions: Discover vetted, open-source repositories optimized for Runpod with minimal setup required.
  • Deploy in one click: Go from discovery to running services in minutes, not days.
  • Customize to your needs: Runpod Hub repos expose configurable parameters for fine-tuning without diving into code.
  • Save development time: Leverage community innovations instead of building from scratch.

​
For Hub creators

  • Showcase your work: Share your projects with the broader AI community.
  • Maintain control: Your GitHub repo remains the source of truth, while the Hub automatically detects new releases.
  • Streamline your workflow: Automated building and testing ensures your releases work as expected.
  • Earn credits from your contributions: Generate Runpod credits when users deploy your repositories. You can earn up to 7% of compute revenue for repos you publish, which is paid directly to your Runpod credit balance based on monthly usage. For more details, see the Revenue sharing section of the publishing guide.

​
How it works

The Hub operates through several key components working together:
  1. Repository integration: The Hub connects with GitHub repositories, using GitHub releases (not commits) as the basis for versioning and updates.
  2. GitHub authorization: Hub repo administration access is automatically managed via GitHub authorization.
  3. Configuration system: Repositories use standardized configuration files (hub.json and tests.json) in a .runpod directory to define metadata, hardware requirements, and test procedures. See the publishing guide to learn more.
  4. Automated build pipeline: When a repository is submitted or updated, the Hub automatically scans, builds, and tests it to ensure it works correctly on Runpod’s infrastructure.
  5. Continuous release monitoring: The system regularly checks for new releases in registered repositories and rebuilds them when updates are detected.
  6. Deployment interface: Users can browse repos, customize parameters, and deploy them to Runpod infrastructure with minimal configuration.

​
Getting started

Whether you’re a veteran developer who wants to share your work or a newcomer exploring AI models for the first time, the Runpod Hub makes getting started quick and straightforward.

​
Deploy a repo from the Hub

You can deploy a repo from the Hub in seconds:
  1. Navigate to the Hub page in the Runpod console.
  2. Browse the collection and select a repo that matches your needs.
  3. Review the repo details, including hardware requirements and available configuration options to ensure compatibility with your use case.
  4. Click the Deploy button in the top-right of the repo page. You can also use the dropdown menu to deploy an older version.
  5. Click Create Endpoint
Within minutes you’ll have access to a new Serverless endpoint, ready for integration with your applications or experimentation.

​
Publish your own repo

Sharing your work through the Hub starts with preparing your GitHub repository with a working Serverless endpoint implementation, comprised of a worker handler function and Dockerfile.
To learn how to build your first worker, follow this guide.
Once your code is ready to share:
  1. Add the required configuration files in a .runpod directory, following the instructions in the Hub publishing guide.
  2. Create a GitHub release to establish a versioned snapshot.
  3. Submit your repository to the Hub through the Runpod console, where it will undergo automated building and testing.
  4. The Runpod team will review your repo. After approval, your repo will appear in the Hub.
Once your repo is approved and published, you can start earning revenue from user deployments. To receive credits, link your GitHub profile to your Runpod account for verified maintainer status. Revenue is calculated monthly based on compute hours generated by your repos, with tiers ranging from 1% (100-999 hours) to 7% (10,000+ hours). Credits are deposited directly into your Runpod account balance each month. To learn more, read the Hub publishing guide.

​
Public endpoints

In addition to offering official and community-submitted repos, the Hub also offers public endpoints for popular AI models. These are ready-to-use APIs that you can integrate directly into your applications without needing to manage the underlying infrastructure. Public endpoints provide:
  • Instant access to state-of-the-art models.
  • A playground for interactive testing.
  • Simple, usage-based pricing.
To learn more about available models and how to use them, see Public endpoints.

​
Use cases

The Runpod Hub supports a wide range of AI applications and workflows. Here are some common use cases that demonstrate the versatility and power of Hub repositories:

​
For AI researchers and enthusiasts

Researchers can quickly deploy state-of-the-art models for experimentation without managing complex infrastructure. The Hub provides access to optimized implementations of popular models like Stable Diffusion, LLMs, and computer vision systems, allowing for rapid prototyping and iteration. This accessibility democratizes AI research by reducing the technical barriers to working with cutting-edge models.

​
For individual developers

Individual developers benefit from the ability to experiment with different AI models and approaches without extensive setup time. The Hub provides an opportunity to learn from well-structured projects. Repos are designed to optimize resource usage, helping developers minimize costs while maximizing performance and potential earnings. In addition, developers who publish their own repos to the Hub can earn credits by participating in the revenue sharing program.

​
For enterprises and teams

Enterprises and teams can accelerate their development cycle by using preconfigured repos instead of creating everything from scratch. The Hub reduces infrastructure complexity by providing standardized deployment configurations, allowing technical teams to focus on their core business logic rather than spending time configuring infrastructure and dependencies. For organizations that contribute their own repos, the revenue sharing program offers an additional incentive, enabling teams to earn credits as their solutions are adopted and used by the wider community.