Two delivery models: run the full stack as a cloud service, or deploy it on your own servers so accounts, messages and recordings stay inside your network Run the full stack on your own servers and keep data inside your network Explore Private Deployment

Developer Center

Manage apps in the console, look up interfaces in the documentation and integrate the SDKs directly; technical support stays with you from the first message to private deployment delivery.

FeiyanCloud developer console overview
Console

From app creation to shutdown, all in one console

Creating an app gives you an AppID and secret, and usage, billing, member permissions and callback configuration all live in the same place; IM and RTC share one console, so there is no switching between backends.

FeiyanCloud developer console overview

App Management

Create apps, view the AppID and secret, configure the callback URL and the development and production environments.

Keys and Security

AppSecret rotation, Token lifetime, IP allowlists and API call auditing.

Usage and Billing

Usage curves for message volume, real-time video minutes, recording and storage, with invoice details you can export for reconciliation.

Members and Permissions

Multi-member collaboration, with read-only, operations and admin roles assigned per app.

Documentation

Copy from the docs and the first line of code runs

The IM documentation includes 48 pages of API cross-reference and 1298 pages of generated content; the RTC documentation runs to 206 pages in Chinese and English. Every quick start gives runnable code and the result to expect.

  • IM Integration Guide
  • RTC Integration Guide
  • Open API Reference
  • Callback Events
server/notify.ts TypeScript
import { FeiyanServer } from '@feiyan/server-sdk';

const client = new FeiyanServer({
  appId: process.env.APP_ID,
  appSecret: process.env.APP_SECRET,
});

// Send a system notification from the server (to all users or specific ones)
await client.message.send({
  from: 'system',
  to: ['user_1001', 'user_1002'],
  type: 'system',
  content: { text: 'Your order has shipped' },
});

// Query today's usage for the app — used for billing reconciliation and alerts
const usage = await client.usage.daily({ date: '2026-11-01' });
console.log(usage.messages, usage.rtcMinutes);

The server SDK is consistent across six languages; swap the sample for Java, Go, Python, .NET or PHP directly.

Integration Guides

Quick starts split by platform: prepare the environment, add the SDK, establish the connection and send the first message.

API Reference

Full parameters and responses for the client API, Open API, admin API and callback events.

Best Practices

Common implementation patterns: paginated conversation lists, message de-duplication, group member sync and recording callbacks.

SDK Downloads

Client, server and UI components are delivered separately, so you take only what you need; version and dependency requirements are listed in each integration guide.

Client SDKs

Web
JavaScript / TypeScript, supporting mainstream browsers
Android
Native SDK and IMKit UI components
iOS
Native SDK and IMKit UI components
macOS
Desktop client
Flutter
One codebase for mobile and desktop
React Native
Integrates directly with an RN project
Mini Program
Mini Program integration

Server SDKs

Node.js
Message delivery, group management, Token issuance
Java
Open API wrappers and callback signature verification
Go
Server-side integration for high-concurrency workloads
Python
Scripts and data tasks
.NET
Windows server environments
PHP
Traditional web backend integration

RTC Platforms and UI Kits

17 platforms
Browsers, mobile, desktop and cross-platform frameworks
React UI Kit
Meeting and call UI components, ready to reuse
Flutter UI Kit
Mobile meeting UI components
Screen sharing
Full screen, window or region granularity

Need a specific version, or an SDK package for a private deployment environment? Say so in a ticket and we will provide the matching build.

Open Source and Samples

Sample projects stay minimally runnable and work as soon as you copy them; the demo apps cover the main IM and RTC scenarios.

IM Demo App

A complete demo with one-to-one chat, group chat, chat rooms and contacts; swap in your AppID and run it.

Try It Online

RTC Scenario Samples

Runnable samples for four scenarios: 1v1 calls, multi-party meetings, interactive live streaming and voice rooms.

Try It Online

Server Call Samples

Server-side sample code for Open API calls, callback signature verification, Token issuance and usage queries.

View Documentation

Client SDKs and UI Components

Integration samples and changelogs for the SDKs, IMKit and UI Kit components on each platform.

View SDKs

Knowledge Base

Troubleshooting paths and conclusions for frequent issues, collected in one place; searching the knowledge base is usually faster than opening a ticket.

Integration and Testing

Troubleshooting paths for AppID configuration, authentication failures, connection failures and multi-platform login conflicts.

Messages and Receipts

Message de-duplication, how read receipts are counted, paginated history retrieval and recall status sync.

Real-Time Video Quality

Locating latency and stalls, bitrate strategy, screen sharing resolution and common causes of recording failures.

Deployment and Operations

Scaling private deployment nodes, database backup, upgrade rollback and log collection.

Billing and Quotas

Metering rules, quota alerts, invoice reconciliation and the invoice request process.

Common Error Codes

What common client and server error codes mean, the likely causes and suggested handling.

Ticket Support

Stuck? Open a ticket

A ticket automatically carries which app and which call are involved; add the request ID and timestamp and support can locate the issue straight from the logs, without going back and forth.

Support Channels

Ticket
The Ticket entry in the console, for technical issues
Email
service@feiyancloud.com
Pre-Sales
service@feiyancloud.com
  1. 1

    Open a Ticket

    Choose the app and issue category under Ticket in the console, and include the timestamp and request ID.

  2. 2

    Triage and Reply

    Support reviews logs and call chains to locate the issue, then provides a fix or an escalation path.

  3. 3

    Wrap-Up and Review

    Once resolved, we share the cause and how to avoid it, and add a knowledge base entry when useful.

Live Sessions

One technical session each month, covering integration details and post-mortems; past sessions can be booked for replay.

  • 2026-10-24 Tech Talk Inside IM Message Delivery: Persistent Connections, Sequence Numbers and Backfill Book a Replay
  • 2026-09-19 Tech Talk Audio and Video on Poor Networks: Bitrate, FEC and Node Scheduling Book a Replay
  • 2026-08-22 Delivery Session Private Deployment in Practice: Offline Installation and Upgrade Rollback Book a Replay

Developer Questions

Is the console account the same as the account on the login page?
It is the same account system. The login page is for the demo; for production, register a developer account in the console and complete business or individual verification, after which you can create apps and get an AppID and secret.
Which versions and runtime environments do the SDKs support?
Clients cover Web, Android, iOS, macOS, Flutter, React Native and Mini Programs; the server side offers Node, Java, Go, Python, .NET and PHP. See each integration guide for exact version requirements and dependencies.
We have no engineering team. Can we use the ready-made UI?
Yes. IMKit and the RTC React / Flutter UI Kits provide finished components such as conversation lists, chat windows and meeting screens; swap in your AppID and it runs, then customise as needed.
How do we get support when something goes wrong?
The Free plan can open tickets, Pro adds a technical liaison group, and Enterprise includes dedicated customer success. For urgent issues, include the request ID and timestamp in the ticket so we can locate it quickly.

Create a Developer Account and Get Your First AppID

The Free plan is enough for integration testing and load testing, and upgrading does not change your code.

Leave Your Details, Get a Plan and a Quote

A pre-sales engineer will go over your use case, concurrency and deployment environment with you, usually within one business day.

Fields marked * are required; we use your details only for this pre-sales conversation.