This project uses Replit’s Clerk Auth integration. We need to access the Clerk dashboard (Build → Tools → Users & Auth → Configure → Advanced → “Open Clerk dashboard”) to configure Native API settings for a published Android app.
When we click “Open Clerk dashboard”, a “Replit Pro Plan” upsell modal appears instead of opening the dashboard.
Questions:
Is Replit Pro (or higher) the only way to access the Clerk dashboard for a Replit-managed Clerk instance?
If the project creator (Replit username: arifvoraji) upgrades to Pro, will they immediately gain access to this instance’s Clerk dashboard?
Is there any other way for the project owner to access or manage the Clerk instance without a Pro plan — for example, by logging into the Clerk dashboard directly?
Is it possible to detach or transfer the Replit-managed Clerk instance to a standalone Clerk account?
We are not asking for a plan upgrade recommendation — we need to understand the technical options.
We contacted Clerk support directly (ticket submitted via the Replit project owner’s account, jedsy2001@gmail.com) and received the following confirmed response from Jordan at Clerk Support:
“Replit applications create a Clerk application automatically. These are managed by Replit directly. You will not have access on your own Clerk account.”
This confirms that our production Clerk instance (Frontend API domain: clerk.licencerummy.com, publishable key prefix pk_live_) is managed exclusively by Replit — and our inability to access the Clerk dashboard via our own Clerk account is expected behaviour.
We therefore need Replit to assist with one of the following:
Option 1 — Unlock Clerk dashboard access for the project owner (Replit username: arifvoraji) without requiring a Pro plan upgrade. Since Replit created this Clerk instance automatically on behalf of our project, we need a supported way to configure it.
Option 2 — Confirm whether upgrading to Replit Pro grants access to the existing production Clerk instance — specifically, the same instance with the same pk_live_ key and existing user data intact. Not a new instance.
Option 3 — Apply these three settings on our behalf to the production Clerk instance (clerk.licencerummy.com):
Enable Native API
Register Android application: package name com.licencerummy.app, SHA-256 fingerprint BA:9F:A9:8C:69:B5:AE:DD:E7:A1:01:D4:81:F4:3D:76:2A:B4:A0:0F:FF:37:2B:35:2F:75:EA:8E:C8:0C:39:BA (from Google Play App Signing)
These settings are required for our published Android app (com.licencerummy.app) to complete Clerk authentication on the Play Store. Our code is already correct and ready — this is purely a dashboard configuration task.
Important: We do not want a new Clerk instance created, and we do not want the existing publishable key changed. We need to retain the existing instance and all its registered user data.
Thanks for the thorough write-up and for getting a direct answer from Clerk support. That quote is the key piece here: Replit-managed Clerk instances stay under Replit’s control, so you will not find your production instance on a standalone Clerk account, and opening a new one would break your existing pk_live_ key and user data.
I will not claim certainty where I do not have it: I cannot confirm whether upgrading arifvoraji to Replit Pro will unlock the dashboard for that existing production instance, so I would not rely on an upgrade as your only path while your Play Store build is waiting.
The channel that can actually touch a Replit-managed Clerk instance is Replit support. My suggestion would be to raise a request via support@repl.it (or status.repl.it for platform issues) naming the exact Frontend API domain and the three settings you listed, and explicitly asking them to apply them to the existing instance without rotating the publishable key or creating a new one. Frame it the way you did here — same instance, same key, users untouched — and include your project owner username. Your format (domain, package name, SHA-256, redirect URI, plus a clear “do not rotate the key” note) is exactly the detail a support team needs to action this cleanly.
One thing worth double-checking on your side while that request is in flight: confirm your Android app’s Clerk SDK is still pointing at the existing clerk.licencerummy.com frontend API and the current publishable key, so you do not accidentally introduce a second domain or key while the dashboard is locked.