Official package · Automation and infrastructure

Terraform provider for realtime apps

Manage apps, webhooks and push notification credentials as code: allowed origins, client events, history, IP allowlists and secret rotation, reviewed in a plan like the rest of your infrastructure.

hibira-io/hibiraTerraform Registry ↗GitHub ↗

• hibira_app, hibira_webhook and hibira_push resources, and data sources for existing apps.
• Rotate an app’s secret with a grace period, so running servers keep working.
• Drift shows up in terraform plan when someone changes an app in the portal.

Sign in to see these snippets with your own cluster host. Sign in

1. Set it up

   terraform {
     required_providers {
       hibira = {
         source  = "hibira-io/hibira"
         version = "~> 0.1"
       }
     }
   }
   
   provider "hibira" {} # reads HIBIRA_API_TOKEN

2. Use it

   resource "hibira_app" "chat" {
     name            = "chat-prod"
     client_events   = true
     allowed_origins = ["https://example.com"]
   }
   
   resource "hibira_webhook" "presence" {
     app_id = hibira_app.chat.id
     url    = "https://example.com/hooks/hibira"
     events = ["member_added", "member_removed"]
   }

Before you start

• Create a token with read and write access on the API tokens page of the portal, and set it as HIBIRA_API_TOKEN.
• The secret is returned once, when the app is created: read it with terraform output -raw. The Free plan has 1 app and needs every origin listed.

Use the app key from your dashboard; the secret stays on your server. Channels, events and authorization endpoints work exactly as they do with Pusher. Create your free account →