Intake
Structured onboarding for the customer, app, repository, and release context.
- Customer and app records
- Bundle ID and Apple team capture
- Repo and build metadata intake
Manual-first release ops for iOS teams
Ship to the App Store without building your own Mac release stack.
SuperSmallApps handles the operational side of App Store publishing for teams that have an app to ship, but do not want to maintain signing, release procedures, and Mac-based submission infrastructure in-house.
1
Manual publish for real launches
Operator-assisted submission for one-off releases and teams that need a reliable human in the loop.
2
Automation setup for repeat releases
Reusable CI/CD-oriented release setup for teams that plan to ship updates regularly over the next year.
3
Security and traceability built in
Encrypted credentials, release history, and auditable operations instead of ad-hoc laptop workflows.
What the service covers
The backend is treated as the source of truth for release operations, so customer onboarding, credentials, release history, and future automation all live in one place.
Credentials
Handling for the artifacts needed to publish without keeping release ops on your laptop.
- App Store Connect API credentials
- Signing assets and profiles
- Encrypted storage and access discipline
Release Ops
A repeatable process for submission instead of fragile one-off instructions.
- Manual-first release orchestration
- Build and submission coordination
- Status tracking and audit history
Offers and pricing
Choose the package that matches how often you plan to ship. Both options keep your Apple account in your name.
Manual Publish
Operator-assisted publishing for teams that need a release handled carefully without standing up long-term automation first.
$50
up to 3 releases
- Onboarding and readiness check
- Credential and signing asset review
- Build and submission coordination
- Operator support for release issues
Auto Publish
CI/CD-oriented setup for teams that want a repeatable release path and less operator friction over the next year.
$99 / year
1 year of automation setup
- Reusable release configuration
- Control-plane records for repeat jobs
- Build-runner integration setup
- Designed to scale from manual to automated releases
Payment access
Pick a package first, then create your portal. Payment instructions are shown only after you are signed in so they stay tied to the correct customer and app record.
Inside your portal
Payment destinations appear only after you open your authenticated customer portal.
- PayPal, crypto, ACH, and Zelle stay linked to the same app intake.
- The operator can review your payment notice in the same workflow.
- Nothing sensitive needs to stay visible on the public start page.
Available methods
Manual payment handling is still supported, but the details are no longer public.
- PayPal remains the default path for most customers.
- Crypto can still be requested when that is the better fit.
- ACH and Zelle stay available for US-based customers who prefer them.
Request-first flow
Start the intake first, then choose the payment method you want once the portal is open.
- Create the portal and add the app.
- Open the app that is still waiting for payment.
- Use the payment instructions shown there, then submit your payment notice.
How it works
The goal is not a generic dev shop handoff. The goal is a controlled release process that can start manually and become automatable later.
01
Choose a package
Pick the one-off manual path or the longer-lived automation setup depending on your release cadence.
02
Send app details
Share the app, Apple account context, repo details, and any current signing assets or gaps.
03
We run the release process
Credentials are organized, the build path is coordinated, and the submission workflow is handled end to end.
04
Keep shipping cleanly
Manual mode stays sellable from day one, while the customer portal tracks plan usage, pending inputs, and later auto-release readiness.
FAQ
Short answers to the main qualification questions people usually have before paying.
Do I need my own Apple Developer account?
Yes. The service does not bypass Apple requirements. Your app stays under your own Apple account.
Can you work without my Apple ID password?
That is the preference. App Store Connect API keys and app-specific credentials are the target path whenever feasible.
Is this only for one app?
No. The backend is being built for multiple customers, multiple apps, and multiple release jobs per app.
Ready to stop treating App Store release ops like a side quest?
Pick a package, create the portal, and then send over the app details. If your case is unusual, contact us first and we will tell you whether manual or automated release support is the right fit.