Compatibility
What works with lomiri out of the box, and what doesn't yet.
Wings
lomiri drives Wings, the node daemon from the Pelican project. The daemon-facing API is frozen to Pelican's contract, so Wings needs no changes or plugins: point it at your lomiri domain and it works as it did with Pelican.
Pelican's eggs (server types) work as they are, and can be imported and exported in the admin panel.
Pelican APIs
lomiri serves the same two public APIs as Pelican, with the same paths, payloads and token format:
| API | Used by |
|---|---|
/api/application | Admin integrations: billing, provisioning, automation |
/api/client | User integrations: bots, scripts, dashboards |
Existing integrations keep working once they have a lomiri API key and your panel URL. For new ones, use the official TypeScript SDK, which works with both lomiri and Pelican. Requests are subject to the rate limiting module when it's on.
Migrating
| From | Status |
|---|---|
| Pelican on PostgreSQL | Supported with the built-in importer. See Migrate from Pelican. |
| Pelican on MySQL, MariaDB or SQLite | Convert a copy of the database to PostgreSQL, then import. |
| Pterodactyl | Not directly. Upgrade to Pelican first (Pelican upgrades Pterodactyl databases), then import into lomiri. |