ml-tooling/opyrator

🪄 Turns your machine learning code into microservices with web API, interactive GUI, and more.

View on GitHub ↗Jump to charts ↓

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 hours ago
Added to GitGenius on September 22nd, 2026
Created on April 6th, 2021
Open Issues & Pull Requests: 7 (+0)
GitHub issues: Enabled
Number of forks: 168
Total Stargazers: 3,133 (+0)
Total Subscribers: 41 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 90.8 days
Mean response time: 91.5 days
90th percentile: 92.2 days
Tracked items: 2

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • stale (2)
  • bug (1)
  • question (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Opyrator is a Python framework that automatically converts machine learning functions into microservices with web APIs and interactive graphical interfaces.

The tool solves the problem of deploying ML code by eliminating boilerplate. It works by analyzing Python function signatures and type hints to automatically generate a web API, an interactive GUI, and other deployment artifacts. Developers write their ML logic as ordinary Python functions with type annotations, and Opyrator introspects those annotations to create the necessary service infrastructure without requiring manual API or interface definitions.

Opyrator suits projects where rapid prototyping and deployment of ML functions matter more than fine-grained control over service architecture. It is particularly useful for data scientists and ML engineers who want to share models or preprocessing pipelines without learning web framework details. The tool works well for internal tools, demos, and proof-of-concept services. Teams building production microservices with complex requirements or those needing extensive customization of API behavior should evaluate whether the automatic generation approach provides sufficient flexibility for their constraints.

The project shows consistent maintenance with regular updates addressing both bug fixes and feature additions. Development includes active engagement with user-reported issues and pull requests, indicating responsiveness to community feedback. The codebase receives ongoing refinement to improve code quality and expand capabilities. Documentation is maintained alongside code changes to keep guidance current with the tool's evolution.