Support
Reploy support has several separate dimensions. A platform can support one dimension without supporting all of them.
App Backend Support
The backend is how Reploy prepares app-provided bundle artifacts.
| Backend | Status | Notes |
|---|---|---|
| Python | Supported | Builds and installs Python wheel bundles, including optional package roots. |
| Other backends | Not yet supported | Future backends should plug into the same bundle lifecycle. |
Runtime Support
The runtime is where the deployed app runs.
| Runtime | Status | Notes |
|---|---|---|
| Docker | Supported | Reploy generates Docker Compose state and controls the app container lifecycle. |
| Native process | Not yet supported | No non-Docker runtime backend exists yet. |
| Kubernetes | Not yet supported | Out of scope for the current release line. |
Host Operating System Support
The host OS determines which binaries are published and which permanent service manager Reploy can use.
| Host | CLI binary | Staging Docker lifecycle | Permanent install/uninstall |
|---|---|---|---|
| Linux | Supported | Supported | Supported with systemd |
| macOS | Deferred | Planned | Deferred; launchd support is undecided |
| Windows | Deferred | Planned | Deferred; Windows service support is undecided |
Current Supported Path
The fully supported path today is:
Python app backend + Docker runtime + Linux host with systemd
Formal macOS and Windows behavior is tracked in the Reploy backlog.