What we're building next.
Nothing on this page is included today. Planned means we intend to build it next; Exploring means we're still working out whether and how. We don't put a date on anything until it's built, and we don't market a feature before then. When something ships, it moves to the changelog.
Next up · planned, no dates
Near term
Scheduling, smarter approvals and better notifications: the next things we intend to build.
-
Planned
Scheduler for automatic actions
Run read-only checks and request routine actions on a schedule you set. Each run follows the same policy and approvals as any other request.
-
Planned
AI assist
Suggested patch plans, and plain-English summaries of what changed and what's still open. Suggestions only: a person approves every change.
-
Planned
Auto-approve within guardrails
Today an admin can let a whole type of action run without approval. Planned: narrower rules, such as by package, severity or time window, always inside each server's own allowlist.
-
Planned
Scheduled restarts and reboots
Today a reboot can be set for a later time. Planned: recurring maintenance windows that restarts and reboots wait for.
-
Planned
Scheduled patch windows
Approved patches wait for a window you choose, so upgrades land when you expect them.
-
Planned
Slack and webhook notifications
Approval requests, results and Patch Proof changes in Slack or any webhook, not only by email.
-
Planned
Patch Proof change digests
A regular summary across your servers: newly open CVEs, fixes that landed, and what still needs a reboot.
2027 and beyond · exploring, no dates
Bigger pieces we're exploring
Heavier work we're researching. Some of it may change shape or not happen.
-
Exploring
Compliance evidence export
Export receipts and Patch Proof history in a form auditors can use for SOC 2 and similar frameworks. An export wouldn't make you compliant on its own.
-
Exploring
Self-hosted or on-prem
Run HostCrust inside your own network or cloud account, for teams that can't use a hosted service.
-
Exploring
Fine-grained policy rules
Policies beyond one setting per type of action: rules per server group, package or time, enforced alongside each server's allowlist.
-
Exploring
Integrations: PagerDuty, Jira, ServiceNow
Open alerts and tickets from HostCrust events, and link approvals to the change records you already keep.
-
Exploring
Drift and anomaly detection
Notice when a server's packages or configuration change outside HostCrust, or when one server behaves unlike the rest of the fleet.
-
Exploring
Fleet-wide staged rollouts
Roll a patch out in stages: a few servers first, each stage checked before the next.
Also on the list
Already announced
These are on the product page's roadmap too. None of them is included today.
Rolling out · no dates
Later · not dated, not included today
FAQ
Roadmap questions
Is anything on this page included today?
No. Everything here is planned or being explored. What works today is on the product page.
When will these features ship?
We don't put dates on anything we haven't built. Items are grouped by how soon we expect to work on them, and that can change.
What's the difference between Planned and Exploring?
Planned means we intend to build it next. Exploring means we're still working out whether and how to build it.
How do I ask for a feature?
Tell us what you need through the talk form, or email hello@hostcrust.com. We read every request.