Beta Notes

What the beta is, what it is not, and what to expect.

---

What is the Beta?

ActionsManager Self-Hosted is currently available as a free beta preview for testing, evaluation, and feedback.

This beta is self-hosted only: it runs on infrastructure you control.

What Beta Means

• The beta is intended for testing, evaluation, and feedback
• Features and limits may change before general availability

Self-Hosted Beta Limits

The following limits apply during the self-hosted beta:

Resource	Beta Limit
Caller Workflow Projects	4
Reusable Workflow Projects	2
Managed Files projects	3
Secrets per project	6
Environment variables per project	6
GitHub environments per project	6
Repositories per project	10
Workflow run history	30 days

These limits are designed to support realistic product evaluation.

No Production Guarantee

The beta is provided as-is, without:

• Warranty
• SLA or uptime guarantee
• Support guarantee
• Production-readiness guarantee
• Enterprise/compliance/security certification

Do not rely on the beta as a guaranteed production service.

What’s Included in the Beta

• Single-container self-hosted deployment
• GitHub PAT and OAuth authentication
• Multi-repository project management
• Workflow management with PR-based delivery
• Drift detection and resolution
• Secrets and variables management
• Real-time WebSocket updates
• Reusable workflow producer/consumer management
• Build type detection and workflow templates

Current Limitations

• Self-hosted only — no hosted/cloud version available in beta
• Single instance — no horizontal scaling or high-availability configuration
• SQLite default — PostgreSQL is supported but not the default
• No formal SLA — no uptime or response time guarantees
• Beta API — API shape may change between releases

Operator Responsibilities

Self-hosted operators are responsible for:

• Securing their deployment and network access
• Using HTTPS when exposing the service beyond localhost
• Protecting GitHub OAuth credentials, personal access tokens, webhook secrets, environment files, database files, and backups
• Configuring GitHub access with least-privilege permissions
• Reviewing workflow changes before applying, merging, or directly committing them
• Choosing target repositories and branches carefully
• Backing up application data before upgrades or configuration changes
• Rotating credentials if they may have been exposed

Providing Feedback

Feedback is welcome during the beta. You can:

• Open an issue to report a bug
• Start a discussion for questions, feature ideas and general feedback

When reporting issues, please include:

• ActionsManager version or image tag
• Deployment method (Docker run, Docker Compose)
• Steps to reproduce
• Expected and actual behavior
• Relevant logs with all secrets and tokens redacted

Upcoming

The beta roadmap is not formally published. Features, limits, and availability may change. Watch the repository for release announcements.

Related Topics

• Installation — getting started with self-hosted
• Security Policy — beta security scope
• Privacy — beta data handling