AppForShareCreate a free account

Choose where your build files live

Team

Where are the files stored? It is one of the first questions on any vendor form, and for teams in Europe the answer often decides whether a tool can be used.

On Team, an Owner or Admin picks where new uploads go: our storage in the United States (the default), our storage in the European Union, or a bucket of your own.

Start freeSee plans

Example

Where your files are

  • New uploadsYour bucket, s3.eu-central-1, acme-builds/appforshare/
  • Builds in the United States214
  • Builds in your bucket37
  • Access keyEnds in 7QX2, sealed
Example values. Builds already uploaded stay where they are.

Made for

  • European teams whose policy asks for files stored in the EU
  • Companies that want test builds in a bucket they control
  • Agencies that must keep a client's builds in the client's storage

What it ends

  • Ruling out a tool because files can only be stored in one country
  • No control over where build files sit or how long they stay

How it works

  1. Step 1

    Open Where your files are

    In Settings, the Owner or an Admin sees where new uploads go now and how many builds sit in each place. Everyone in the workspace can see it.

  2. Step 2

    Pick a place

    United States (Google Cloud us-east4), European Union (Google Cloud europe-west), or your own bucket.

  3. Step 3

    For your own bucket, test it

    Enter the endpoint, region, bucket, folder and an access key. Before saving, AppForShare writes, reads and deletes one small file under the folder.

What goes there

The build files: the .ipa, the .apk and the kept .aab. Install pages, icons, feedback files and analytics stay on AppForShare. Builds you uploaded before a change stay where they are; nothing is moved.

If the chosen place cannot be written, the upload fails with a clear message. Files never land somewhere else instead.

Your own bucket

Amazon S3, any S3 compatible service, or Google Cloud Storage with an HMAC key. AppForShare writes only <folder>builds/<build>/ objects, never lists the bucket, and deletes only the files of a build that was deleted or expired, after the usual 7 day restore window. Testers download through a signed link valid for 10 minutes.

Keys are encrypted with Google Cloud KMS and never shown again; the page shows the last 4 characters of the key ID only. Disconnecting sends new uploads back to our storage; builds in your bucket keep working until they are deleted. Deleting the workspace never deletes anything in your bucket except our build files.

Good to know

Questions

Where are files stored by default?
On Google Cloud Storage in the United States (us-east4), in a private bucket, served only through signed, short lived links.
Are my existing builds moved when I switch?
No. Builds already uploaded stay where they are. Settings counts builds per place.
Which buckets work?
Amazon S3, S3 compatible services, and Google Cloud Storage with an HMAC key.
Can AppForShare read the rest of my bucket?
It never lists the bucket and only writes and deletes files under the folder you give, for its own builds. Give the key access to that folder only if your provider allows it.
Which plan do I need?
Team.

Read next

Try it on your own app

Free account in a minute. Pro starts with a 7 day free trial.

Create a free accountPricing

More features