Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience real numbers from our own analytics — open to see them
–Visitors
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · counted by iTechGuides's own first-party analytics, bots removed, every figure rounded down · how we count

Satis review

Free#49 of 63 in Artifact Repository Software

A focused, self-hosted registry builder for private PHP package distribution.

6.0/10Editor score
Satis6.0 Visit Satis

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

Satis is an open-source tool for PHP developers and organizations that need private Composer package repositories. It reads configured VCS, Composer, artifact, path, and package repositories, then generates a static Composer registry that the customer can host. Its scope is deliberately focused: Satis is designed for private PHP dependencies, not general-purpose binary or container artifact storage.

The repository-building workflow covers more than metadata generation. Satis can select all packages or specific packages and versions, resolve package and development dependencies, and create local ZIP or TAR archives. Package whitelists and blacklists provide control over what enters the generated repository, while partial repository updates can limit the work required for changes. Provider and include metadata files support the structure expected by Composer clients. These capabilities make Satis a practical fit when a team wants a curated private package source instead of a broad artifact-management system.

Deployment stays with the customer. Satis can run from source, through Composer installation, or with Docker, and its output can be served through a web server or Docker-based deployment. The published positioning is therefore a self-hosted, customer-managed setup rather than a hosted SaaS service. Basic access control is available, but teams needing broader artifact types or more extensive permission management should consider an alternative category of repository platform. Choose Satis when Composer compatibility, dependency resolution, static output, and control over repository contents are the priority; avoid it when the repository must serve containers, binaries, or a wider range of development artifacts.

Satis pros and cons

  • Where it wins
    • Aggregates VCS, Composer, artifact, path, and package repositories
    • Resolves dependencies and generates provider and include metadata
    • Builds local ZIP or TAR archives with package filtering controls
  • Where it doesn't
    • Composer-only scope does not cover general artifact storage
    • Customer-managed hosting requires a self-hosted deployment
    • Access control is basic rather than an extensive permissions system

Satis fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. We may earn a commission when you click some links. How we rank.

Last updated · How we research and update