A project is the first thing you create in Livqeno. It's a container for one app: every room, conversation, live stream, API key, and webhook you make lives inside it. Projects never share data with each other.
Where this fits: project → API key → your backend makes tokens → your app joins. You can't make an API key, and so can't do anything else, until you have a project.
One project or several?
Make one project per app. Inside it you already get separate development, staging, and production spaces (see below), so you don't need extra projects for testing.
| Situation | What to do |
|---|---|
| One app, tested locally and then launched | One project. Use its environments. |
| Two unrelated apps (say, a dating app and a telehealth app) | Two projects, so their data, keys, and usage stay apart. |
| One app, but a separate team or customer must never see the other's data | Separate projects. |
Create a project
- Open the dashboard and sign up.
- Create a project from the projects screen.
Livqeno picks the project id for you.
npm install -g @livqeno/cli
livqeno config set apiUrl https://api.livqeno.com # once: the CLI defaults to localhost
livqeno login
livqeno projects create my-video-appEvery new project comes with three environments, already set up: development, staging, and production. They are kept fully apart: a development key can't see production rooms or messages. You can't add more environments. See Environment.
Set up the CLI
Use the CLI if you prefer the terminal, or want to script your setup. The commands in the CLI tab above run on your computer.
livqeno projects create prints the new project's ID, a UUID like
16281d1e-5b0c-4f3e-9a51-7d2c8e4b9a10. Keep it for the next step.
livqeno login opens your browser and uses your dashboard login.
No browser on the machine (for example, a CI server)? Set LIVQENO_TOKEN
instead. See CLI.
Then select the project, so later commands (like livqeno keys create) know
which one to use. projects use takes the project ID:
livqeno projects list # shows each project's ID
livqeno projects use <project-id>Skip this and livqeno keys create fails with "No Livqeno project selected".
Or link the current folder to a project. This writes a small config file, so
anyone running livqeno in this folder uses the same project:
livqeno initIt writes swalvo.json in the current folder. The file holds only the
project id, never a secret, so it's safe to commit.
What belongs to a project
| Thing | Notes |
|---|---|
| Rooms and conversations | Names are per project. Two projects can both have a support room without clashing. |
| API keys | Revoking a key in one project doesn't affect others. |
| Webhooks | Set per project and per environment. |
| Connections, errors, usage | Shown per environment, so test traffic doesn't mix with real traffic. |
| Audit log | Records every admin action, and who did it. |
Who can manage the project (add keys, invite teammates, delete it) is set by roles. See Roles & permissions.
Next steps
You now have a project. Next, give your backend a way to talk to it: