Venelx Docs
AI setupSign up

Getting Started

From zero to your first build in five steps.

1. Create your account

Sign up at app.venelx.com. If you are asked to verify your email, confirm the link in your inbox before continuing.

Set up with AI. Prefer to let your AI assistant do steps 2 to 5? Paste one prompt into Claude Code, Cursor or any MCP client and it creates the project for you. See Set up with AI.

2. Connect GitHub

In the dashboard, go to Account → GitHub (or the banner prompting you to connect) and click Connect GitHub. Venelx uses a GitHub App OAuth flow — you authorize the app and pick which repositories Venelx can see.

You don't need to manage tokens: Venelx renews expiring GitHub credentials automatically. Read the full story in GitHub connection.

3. Create a project

Projects → New project, then:

  1. Pick a repository from your connected GitHub account.
  2. Choose the platforms to build: iOS, Android, and/or web targets.
  3. Set per-project environment variables (API URLs, EXPO_PUBLIC_*, and optionally a project-level GITHUB_TOKEN — see credential priority).

4. Configure signing (production builds only)

Preview builds run unsigned. For store-ready artifacts, set up signing once per platform:

  • iOS — save an App Store Connect API key and Venelx auto-provisions the certificate, provisioning profile, and .p12 at build time. See iOS signing.
  • Android — upload your keystore with its alias and passwords. See Android signing.

5. Run your first build

From the project page, click Build and pick a platform (e.g. ios-production or android-production). You can watch the build live:

  • Logs stream in real time into the dashboard log viewer.
  • When the build finishes, the artifact (.ipa, .aab/.apk, …) appears under the project's Files page for download.

Builds run on Venelx shared workers by default, with nothing to set up. To run them on your own Mac, Windows or Linux machine, add a worker under Account → Self-hosted workers (see Build workers). Per project, Settings → General → Worker routing picks Hybrid (your workers first, then Venelx shared workers) or Strict (only your workers).

You can also trigger builds from an AI assistant with the MCP server (trigger_build), or over HTTP with an API token.

← IntroductionSet up with AI →