Fondoo
GitHubStart your 7-day trial for $0Start trial
Docs

Connect Fondoo Cloud to Fondoo

cloudComing soon2 min readUpdated

Fondoo Cloud is listed as a choice for your app's backend. The backend is where Fondoo would sync your users' sign-ups and paid plans. Today it is only a placeholder. It asks for no credentials, runs no vendor actions and stores no data. If you need a working backend connection now, use Supabase or Firebase instead (see below).

What Fondoo can do with it

Nothing yet. In the code, Fondoo Cloud is:

  • one of three backend choices, alongside supabase and firebase;
  • the value get_providers reports as your selected backend by default, when you haven't chosen one. This default is only a label. It does not turn on any feature or block anything.

Fondoo marks it as a placeholder in its connection guide. No owner approval is involved because there are no actions to approve.

Before you start

Not applicable yet. You don't need an account, plan or keys.

If you want working backend sync today, have one of these ready instead:

  • a hosted Supabase project URL and a server-only service key; or
  • a Firebase service account (project ID, client email and private key).

Step by step: get your credentials

Not applicable. Fondoo Cloud asks for no credentials.

For a working backend, follow supabase.md or firebase.md in this folder. The owner then connects it with connect_backend. That operation is owner-only and has to be done by a person, not an agent.

Connect it in Fondoo

(a) Dashboard. Fondoo Cloud does not appear on the Connections page. Supabase and Firebase do: they're under Development in the Available card.

(b) Ask your agent. Example prompt:

Which backend is my site using, and is Fondoo Cloud available yet?

The agent runs:

  • get_providers({siteId}), which returns choices.backend and selected.backend.
  • connect_service({provider: "fondoo_cloud", siteId}), which returns placeholder: true and the step "This connector is a placeholder. No credentials are requested and no vendor action is available yet."

REST equivalent:

curl -X POST https://api.getfondoo.com/v1/ops/get_providers \
  -H "Authorization: Bearer $FONDOO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"siteId":"YOUR-SITE-UUID"}'

Avoid this: don't explicitly choose Fondoo Cloud with set_provider({capability: "backend", provider: "fondoo_cloud"}) if you already have a Supabase or Firebase backend connected. Fondoo checks that the backend it syncs to matches your chosen one. If they don't match, plan and sign-up syncs stop with "Selected backend connection is missing". If you use Supabase or Firebase, either never set a backend choice, or set it to supabase or firebase.

Test that it works

There is nothing to test for Fondoo Cloud itself. To check your status:

  1. get_providers shows which backend is selected.
  2. connect_service for fondoo_cloud shows placeholder: true. When that changes to false, it's available.

Troubleshooting

  • "Selected backend connection is missing." Your backend choice doesn't match the backend you connected. The owner runs set_provider with capability: "backend" and the provider you actually connected.
  • No connect button for Fondoo Cloud. That's expected. It's not offered on the Connections page yet.
  • connect_backend rejects fondoo_cloud. That's expected. connect_backend only accepts supabase or firebase.

Limits, data and security

Fondoo stores no credentials or data for Fondoo Cloud. The only thing saved is your backend choice, and only if you set one with set_provider. You have nothing to rotate or disconnect. To undo a choice, set the backend to the provider you actually use.