devpi-server

devpi-server is a self-hosted Python package index and build coordination server (part of devpi) that provides package upload, indexing, and environment/workflow features for managing Python package releases (including multiple indexes and stages).

Evaluated Apr 04, 2026 (20d ago)
Homepage ↗ Repo ↗ Infrastructure python package-index devpi artifact-repository self-hosted pypi-compatible repository-management staging-promotions
⚙ Agent Friendliness
34
/ 100
Can an agent use this?
🔒 Security
59
/ 100
Is it safe for agents?
⚡ Reliability
36
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
0
Documentation
30
Error Messages
0
Auth Simplicity
55
Rate Limits
20

🔒 Security

TLS Enforcement
80
Auth Strength
65
Scope Granularity
40
Dep. Hygiene
50
Secret Handling
55

As a self-hosted service, security depends heavily on deployment configuration (TLS termination, reverse proxy settings, authentication/authorization configuration, network controls, and operational hardening). The supplied data does not include evidence of fine-grained scoped permissions, formal secret-handling guarantees, or security posture details.

⚡ Reliability

Uptime/SLA
0
Version Stability
60
Breaking Changes
40
Error Recovery
45
AF Security Reliability

Best When

You need reproducible internal Python package distribution with staged promotion and isolation, and you can run/operate a self-hosted service.

Avoid When

You only need static artifact hosting or you cannot operate a server component with appropriate security and maintenance practices.

Use Cases

  • Host and manage internal Python package repositories and indexes
  • Promote packages through stages (e.g., dev -> staging -> production)
  • Support teams in building, uploading, and consuming Python packages consistently
  • Create controlled package workflows for CI/CD

Not For

  • A managed/public package index replacement without self-hosting
  • Use as a general-purpose file storage service
  • Use without understanding Python packaging/index concepts and configuration

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
No
SDK
No
Webhooks
No

Authentication

Methods: HTTP basic auth (commonly used in devpi deployments) Authentication via configured devpi users/permissions (implementation/config dependent)
OAuth: No Scopes: No

Authentication mechanisms are configuration- and deployment-dependent; no explicit OAuth/scoped API auth information is provided in the supplied data.

Pricing

Free tier: No
Requires CC: No

Self-hosted open-source software; costs are infrastructure/operations rather than vendor pricing.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • No MCP server/interface contract provided in the available data, so agents must rely on whatever HTTP UI/API the deployment exposes.
  • devpi is typically operated with configuration and policies; automated agents should expect environment-specific behavior and require careful handling of credentials and permissions.
  • Package upload/index operations may not be idempotent depending on workflow and versioning/promotion rules.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for devpi-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered