I'm not familiar with Rundeck, but a quick google search makes me think it's a very different tool.
Technical teams use Hookdeck to receive webhooks reliably. However, Hookdeck itself makes no assumption about what those webhooks are used for or do (we don't run workflows). You can think of it as the backbone/infrastructure to manage and run your asynchronous events without having to put together queues, workers, ingestion services, alerts and logs.
