Roadmap

What we are building next.

Deenez is evolving around safer DNS operations, better provider coverage, and clearer team workflows.

Timeline

Prioritized around safer DNS operations.

The order can shift based on customer demand, but these are the items currently closest to the product direction.

Next up Provider connection

Connect AWS Route 53 domains to the same Deenez workflow used for your other DNS providers.

Import hosted zones and records from Route 53.
Prepare and publish DNS changes through the Deenez workflow.
Keep provider-specific details visible without turning Route 53 into a separate process.

Next up Email DNS

Flatten include-heavy SPF records into provider-ready DNS values while keeping the original sender intent maintainable.

Planned Operations

Monitor important DNS-backed services so teams can catch availability problems after changes and migrations.

Planned Scheduled changes

Automatically lower TTLs before scheduled DNS changes and restore them afterwards to make rollouts safer.

Planned Notifications

Send DNS workflow updates to Microsoft Teams channels so review requests, scheduled changes, and operational alerts stay visible.

Route DNS notifications to the Teams channels your organization already uses.
Notify teams about review requests, completed publications, and scheduled changes.
Keep DNS operations visible without requiring everyone to watch Deenez directly.

Planned Notifications

Connect Deenez to Discord for teams that coordinate infrastructure and incident work from Discord servers.

Have a request?

If your team needs a specific DNS provider, workflow, notification target, or operational safeguard, send it over so we can prioritize it properly.