Frequently Asked Questions

Common questions about BeatConnect’s SDK and developer tools.

General

What is the BeatConnect SDK?

The BeatConnect SDK is a complete infrastructure for building, signing, and distributing audio plugins. It includes:

Cloud builds for macOS and Windows
Automatic code signing and notarization
License activation API
Distribution through BeatConnect marketplace (optional)

Do I need coding experience?

For the visual Plugin Builder: No coding required. Build plugins using our visual node-based interface.

For the SDK: Yes, you need C++ experience and familiarity with audio plugin development (JUCE framework).

What frameworks are supported?

Framework	Support Level
JUCE + CMake	✅ Full support
JUCE + Projucer	⚠️ Requires migration to CMake
iPlug2	🔜 Coming soon
Other CMake-based	⚠️ Contact us

Can I use my existing JUCE project?

Yes! If your project uses CMake, you can integrate directly. If you use Projucer, follow our migration guide.

Builds

How long does a build take?

Plugin Complexity	Typical Time
Simple (few files)	3-5 minutes
Medium	5-8 minutes
Complex (many files)	8-15 minutes

First builds may take longer due to cache population.

What platforms are supported?

macOS: Universal (Intel + Apple Silicon), Intel-only, or Apple Silicon-only
Windows: x64

Linux builds are not currently supported.

What formats are supported?

VST3 — All platforms
AU (Audio Units) — macOS only
Standalone — All platforms
AAX — Requires separate Avid developer agreement

Are builds automatic when I push to GitHub?

Optional. You can configure automatic builds on push, or trigger manually from the Creator Portal.

What happens to my source code?

Your code is:

Cloned from GitHub
Compiled
Immediately deleted

We never store your source code. Only the compiled, signed binaries are kept.

Can I use private repositories?

Yes. Install the BeatConnect GitHub App and grant access to your private repos.

Code Signing

Do I need my own Apple Developer Account?

No. BeatConnect provides code signing for all builds:

macOS: Developer ID + Notarization
Windows: Authenticode (EV certificate)

This saves you $99/ ye a r (A ppl e) +$ 200-500/year (Windows certificate).

Will my plugins work on Gatekeeper-protected Macs?

Yes. All macOS builds are notarized by Apple, so they work immediately without security warnings.

Can I use my own code signing certificate?

Enterprise plans support custom certificates. Contact sales for details.

Are plugins signed immediately or do I need to wait?

Signing happens during the build. Notarization typically adds 2-5 minutes.

License Activation

How does license activation work?

Build with enableActivationKeys: true
Customers purchase and receive an activation code
Your plugin calls our API to activate
We track activations per machine

How many activations per license?

You configure this when generating codes. Common choices:

2 machines (typical for individual users)
5 machines (for studios)
Unlimited (for enterprise)

Can users deactivate and move licenses?

Yes. The API supports deactivation, freeing up the slot for a new machine.

What if a user’s computer dies?

Options:

User contacts you to reset activations
You can revoke and issue a new code
Provide a “reset activation” option in your plugin

Is there offline activation?

Yes. Implement offline activation flow:

Plugin generates an activation request
User sends it to your support
You generate an offline response
User enters the response in the plugin

See Offline Activation.

Pricing & Billing

How much does it cost?

Developer Tier: $29.99/month

5 builds per month
$5 per additional build
All features included

What counts as a build?

One build = one trigger, regardless of platforms/formats selected. Building for macOS + Windows in one trigger is one build.

Do failed builds count against my quota?

Your code errors: Yes
Our infrastructure errors: No

Can I cancel anytime?

Yes. Cancel from the Creator Portal. You keep access until the end of your billing period.

Is there a free trial?

New creators get their first build free to test the system.

Distribution

Do I have to sell on BeatConnect?

No. Built plugins are yours to distribute anywhere:

Your own website
Other marketplaces
Free distribution

BeatConnect marketplace is optional.

Can I sell on multiple platforms?

Yes. There’s no exclusivity requirement.

How do payouts work for marketplace sales?

If you sell through BeatConnect:

Connect Stripe account
We handle payment processing
Automatic payouts to your bank

What’s the marketplace fee?

See our pricing page for current rates.

Technical

What CMake version is required?

CMake 3.22 or higher.

What JUCE version is supported?

JUCE 7.0 and higher. Earlier versions may work but are not tested.

Can I use third-party libraries?

Yes, as long as they:

Support macOS arm64 (for Universal builds)
Can be compiled from source or are statically linked
Are properly licensed for distribution

How do I include binary resources?

Use JUCE’s binary data system:

juce_add_binary_data(PluginResources
    SOURCES
        Resources/image.png
        Resources/preset.xml
)
 
target_link_libraries(MyPlugin PRIVATE PluginResources)

Can I use SIMD/vectorization?

Yes. The build system supports:

SSE/AVX on Intel
NEON on Apple Silicon

Use runtime detection for cross-platform code.

How do I debug build failures?

Download build logs from Creator Portal
Look for the first error (not warnings)
Test locally with the same CMake configuration
See Troubleshooting Guide

Account & Access

How do I become a creator?

Sign up at beatconnect.com
Apply for creator access
Subscribe to Developer tier

We recommend one account per developer. For teams:

Each developer has their own account
Use GitHub organization for shared repos
Consider Team tier for higher limits

How do I connect GitHub?

Creator Portal → Settings → Developer
Click “Connect GitHub”
Authorize the BeatConnect GitHub App
Select repositories to grant access

Can I connect multiple GitHub accounts?

Yes. You can connect personal and organization accounts.

Support

Where can I get help?

Documentation: docs.beatconnect.com
Discord: BeatConnect Community
Email: support@beatconnect.com

How fast is support response?

Discord: Usually within hours
Email: Within 1-2 business days
Critical issues: Prioritized for faster response

Is there an SLA for enterprise?

Enterprise plans include guaranteed response times. Contact sales.

Comparison

How is this different from JUCE’s CI/CD?

JUCE provides the framework. BeatConnect provides:

Pre-configured build infrastructure
Code signing included (no certificates needed)
Apple notarization handled
License activation system
Distribution marketplace (optional)

How is this different from GitHub Actions?

GitHub Actions requires:

Complex workflow configuration
Your own code signing certificates
Apple Developer Account for notarization
Manual setup for license activation

BeatConnect handles all of this out of the box.

Can I use BeatConnect with my existing CI/CD?

Yes. Trigger builds via API from your own CI/CD pipeline.

Feature Requests

How do I request a feature?

Discord: Post in feature-requests
Email: features@beatconnect.com
GitHub: Open an issue on our public roadmap

What’s on the roadmap?

Check our public roadmap at beatconnect.com/roadmap.

Common requests in progress:

iPlug2 support
Linux builds
AAX format improvements
Team collaboration features

BeatConnect Docs

Explorer

FAQ