Backendless

Install corsair and @corsair-dev/backendless, add the Backendless plugin, and connect with your credentials. Then call methods like corsair.backendless.api.counters.get() from your app. Corsair syncs data per tenant.

Yes. Backendless supports your credentials. Use credentials or OAuth scopes that match what you automate. Create them in the Backendless developer console, then paste into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Backendless, GitHub, Notion, Stripe, and the rest. Trigger Backendless from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for backend-as-a-service for databases, user auth, file storage, and serverless logic. Common builds include sync jobs, admin tooling, and agents that call Backendless APIs from your backend. Local DB entities let you query synced Backendless records without hitting the API on every read.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Backendless API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/backendless in the open repo. When Backendless ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Backendless data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Backendless data on your behalf.