Migrate
Already live somewhere? We translate the calls.
Migration tools convert SDK calls from the most common alternatives. Drop your code in and get a Kardolive port — same method shape, same callbacks, same event names. No two-quarter rewrite.
Four steps
From someone else’s stack to yours.
01
Run the migrator
kardolive migrate --from agora --in ./src scans your code and writes a Kardolive port to ./out.
02
Review the report
It lists what mapped, what needs a look, and what has no equivalent — flagged inline with TODO comments.
03
Run both
Keep both stacks side by side for a week or two and move traffic over gradually.
04
Cut over
When the numbers match or beat the old stack, move the rest.
Where we translate from
Ten source platforms today. Ask for yours.
From Agora
Method-level mapping for RTC and RTM.
From ZEGO
Express SDK and rooms API, with the same event shape.
From Twilio Video
Room, Participant and Track mapped one to one. Recording rules carry over.
From Vonage / TokBox
Session, Stream and Subscriber translated; unsupported callbacks flagged.
From Mux
Live and asset abstractions; playback IDs become signed room links.
From Wowza
RTMP ingest config and transcode ladders imported.
From Tencent Cloud
TRTC and Cloud Live — the same protocols, on our infrastructure.
From Alibaba Cloud
Live and RTC mapped; region routing handled by placement.
From Vhall
Webinar SDK with Q&A, registration and reporting.
From Polyv
Education SDK with classroom, breakout and whiteboard equivalents.
Stop staring at the rewrite ticket.
Run the migrator on a branch, see how much converts, and decide from there.