Yes, completely free. GitHub Actions provides free compute for public repositories, and we pass that savings to you. There are no hidden fees, no premium tiers, and no rate limits.

Is it safe to upload my keystore?

Your keystore is uploaded securely via HTTPS, used only during the signing process, and deleted immediately after. The workflow runs in an isolated GitHub Actions environment that is destroyed after each job. You can verify this in our open-source code.

Why do I need to sign my AAB?

Google Play requires all apps to be signed with your private key. If you're using a build system that produces unsigned bundles, or if you need to re-sign an AAB, you'll need to sign it before uploading to Play Console.

What tools do you use for signing?

We use jarsigner from the official Java SDK with SHA256withRSA signature algorithm - the same process Google recommends for signing Android App Bundles.

Can I use this for production apps?

Absolutely. This tool produces production-ready signed bundles suitable for Google Play release, signed with jarsigner exactly as Google recommends.

Where can I get a keystore?

You can generate one using Android Studio (Build > Generate Signed Bundle/APK) or the keytool command line utility. If you've previously published to Google Play, use the same keystore to maintain update compatibility.

Sign your Android App Bundle

Upload the unsigned .aab and the keystore you built it with, add the alias and passwords, and you get a signed bundle back in about thirty seconds. Your keystore is used once and deleted when the job ends.

Signing runs as a public GitHub Actions job using jarsigner with SHA256withRSA, then the machine and both uploads are destroyed. Read the workflow

Questions

It travels over HTTPS, is used for one signing job, and is deleted as soon as that job ends. The job runs on a GitHub-hosted machine that is destroyed afterwards. The workflow file is public, so you can read exactly what touches it.

jarsigner from the official Java SDK, using SHA256withRSA. The same tool and algorithm Google documents for App Bundles.

Yes. The output is a production-ready signed bundle, suitable for a Play Store release.

Android Studio generates one under Build, then Generate Signed Bundle or APK. The keytool utility does the same. If your app is already on Google Play, reuse the keystore you published with, or updates will be rejected.

Yes. GitHub Actions gives public repositories free compute, and that is what runs the signing. No accounts, no tiers, no rate limits.

Something not working? support@testerscommunity.com