Connection explainer · App Store Connect

Connect Tazuki to Xcode Cloud with an App Store Connect API key.

Tazuki uses App Store Connect as the connection point for the Xcode Cloud data it can synchronize. The setup is deliberately split between a provider credential, secure local storage, and a local history workspace.

See how it works

What it is

Provide an App Store Connect API key, then let Tazuki validate and discover the available projects.

The connection uses an Individual App Store Connect API Key: a .p8 private key and Key ID. After validation, Tazuki can discover projects and synchronize available Xcode Cloud history while keeping the credential in macOS Keychain and normalized facts in local SQLite.

At a glance

The useful shape of this capability.

What Tazuki needs

An Individual App Store Connect API Key, including the .p8 private key and Key ID.

After connection

Validation, project discovery, and synchronization of data available through the provider.

Local boundary

Credentials stay in macOS Keychain; synchronized facts and connection history use local SQLite.

What Tazuki needs

Use an App Store Connect API key to connect Tazuki to Xcode Cloud.

Tazuki does not create a parallel cloud account. It uses the App Store Connect API key you provide to request the Xcode Cloud data your Apple permissions make available.

  • Individual App Store Connect API Key
  • .p8 private key
  • Key ID

After connection

Validate the .p8 key, discover projects, then synchronize Xcode Cloud data.

The connection has a clear sequence: validate the credential, discover the projects available through App Store Connect, and synchronize the Xcode Cloud history the source provides.

  • Credential validation
  • Project discovery
  • Synchronized project and build data

Stored locally

Store the private key in macOS Keychain and history in local SQLite.

Tazuki uses macOS Keychain for the private key. The normalized facts and connection history that support the workspace are stored in local SQLite, while the original .p8 path is not persisted.

  • macOS Keychain credential storage
  • Local SQLite facts and connection history
  • Original .p8 path not persisted

A useful boundary

Connection does not replace Apple permissions.

Tazuki is a Mac workspace around App Store Connect and Xcode Cloud data. It does not change Apple permissions, expose credentials on the website, or become the provider of build data.

  • No credential setup through this website
  • No real Key ID or .p8 material in product content
  • No replacement for Apple account permissions

Questions, answered

A capability with clear edges.

How does the App Store Connect API connect Tazuki to Xcode Cloud?

Tazuki validates the Individual App Store Connect API key you provide, discovers the Xcode Cloud projects available to that connection, and then synchronizes the source data it can access.

What does Tazuki need from App Store Connect?

Tazuki uses an Individual App Store Connect API Key, including the .p8 private key and Key ID, to validate the connection and discover the available Xcode Cloud projects.

Where are the credentials stored?

The private key is stored in macOS Keychain. The original .p8 file path is not persisted in the local SQLite facts database.

Does connecting Tazuki change Apple permissions?

No. Tazuki uses the credentials and permissions you provide through App Store Connect. It does not replace Apple account permissions or create a separate authorization system.

Tazuki · macOS 14+

Keep the useful context close.

Tazuki is available on the Mac App Store. Download it free and unlock remote synchronization with Pro.

Download on the Mac App Store