Simple credit pricing for builds and voiceovers

APKBuild uses one credit wallet for everything: one credit is one US cent, an APK build costs 10 credits, an AAB costs 15 and a rebuild costs 5. The same balance pays for AI voice generation. There is no free tier — every build is paid for with credits or a plan.

A single app can be bought on its own for $2.50 once, with no subscription and nothing on file to renew; a plan from $9/month suits repeat work and adds monthly credits, priority queueing and unbranded artifacts.

What a single app costs

There is no free tier, and no card is needed to create an account: a build runs once credits are on the wallet. A single app is $2.50 once — 10 credits, no subscription — and the one-time pack is a single charge that never auto-renews.

Paid work is unbranded: the same Gradle release build runs in the same container, the log is just as readable, and the project is stored so a rebuild is one click. A rebuild costs 5 credits instead of 10 because the icon, source and signing key are already stored.

What each build costs in credits

One credit equals one US cent. An APK build costs 10 credits (about $0.10), an AAB build costs 15 credits (Google Play output), and a rebuild of an existing project costs 5 credits because the icon, source and signing key are already stored.

In plan terms: Starter’s 70 monthly credits are seven APK builds, Pro’s 200 credits are twenty, and Agency’s 500 credits are fifty. Voice generation draws on the same balance, so an account that builds an app and records a demo voiceover is spending from one number, not two subscriptions.

The three plans

Starter is $9 a month for 70 credits, removes the APKBuild branding from your artifacts and covers a single small app or a first client project. Pro is $19 a month for 200 credits and adds priority in the build queue — the difference you notice when a deadline is close and the queue is busy. Agency is $35 a month for 500 credits with the highest queue priority, sized for teams running several client apps and voiceovers every month.

Monthly credits reset on the 1st. Plans are self-serve: switch tier or cancel from your account, and the project data — apps, icons, banners, signing keys — stays where it is.

Payment methods and failed builds

Card payments, Binance Pay and crypto are supported at checkout. The one-time single-app pack is a single charge with nothing stored to renew; subscriptions renew monthly until cancelled.

If a build fails for a platform reason — a container restart, a toolchain error on our side — the credits for that build are returned to your account. A build that fails because of an input problem (a non-HTTPS URL, a ZIP without index.html, an invalid package ID) is visible in the log with the stage that rejected it, so the fix is in your hands rather than in a support queue.

Frequently asked questions

Do I have to subscribe to build an app?

No. A single app can be paid for on its own: the one-time pack is $2.50 for 10 credits, no subscription and no auto-renewal. Subscriptions from $9/month are for repeat work — they add a monthly credit wallet, priority queueing and unbranded artifacts.

How do credits work across builds and voiceovers?

One credit is one US cent and one balance covers everything: 10 credits for an APK, 15 for an AAB, 5 for a rebuild, and voice generation priced per generation. Plan credits are added monthly and reset on the 1st.

What payment methods do you accept?

Card payments, Binance Pay and crypto. Plans are self-serve and cancel from your account; the one-time pack is a single charge with nothing stored to renew.

What happens if a build fails?

Every build streams its log into the console, so an input problem — non-HTTPS URL, ZIP without index.html, malformed package ID — is visible with the failing stage. If the failure is on our side, the credits for that build are refunded to your account.