Sign Your Android App Bundle
in Seconds
Upload your unsigned AAB, provide your keystore, and get a signed bundle ready for Google Play. Powered by GitHub Actions.
Sign Your AAB
Your keystore and passwords are used only during signing and are immediately deleted. We never store your credentials.
How It Works
Simple, transparent, and secure signing process
Upload Your Files
Drop your unsigned AAB and keystore file. Everything stays secure until submission.
Secure Processing
Files are temporarily uploaded to trigger a GitHub Actions workflow. Deleted immediately after.
Automated Signing
GitHub Actions runs jarsigner to properly sign your bundle - the same tools Google recommends.
Download & Publish
Get your signed AAB ready to upload directly to Google Play Console. That's it!
From the makers of Testers CommunityNeed Testers for Google Play?
Getting production access on Google Play requires 12 testers for 14 consecutive days. Finding reliable testers is hard - we make it easy.
Fully Open Source & Transparent
See exactly what happens to your files
Inspect Our Code
Every line of code is public. Check the GitHub Actions workflow file to see exactly what runs on your files - no secrets, no hidden logic.
No Data Storage
Files are processed in ephemeral GitHub VMs and deleted immediately. We don't store your AAB, keystore, or any credentials. Ever.
Community Trusted
Used by thousands of Android developers. Part of the Testers Community ecosystem trusted by 15,000+ developers.
Watch It Happen
Real-time visibility into the signing process. Every workflow run is public - you can see exactly what code runs on your files.
Don't trust us? Check the workflow yourself - it's all open source.
View Live Workflow RunsFrequently Asked Questions
Everything you need to know about AAB signing
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.
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.
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.
We use jarsigner from the official Java SDK with SHA256withRSA signature algorithm - the same process Google recommends for signing Android App Bundles.
Absolutely! This tool produces production-ready signed bundles suitable for Google Play release. Thousands of developers use this tool for their production apps.
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.
Still have questions or running into issues?
support@testerscommunity.com