Start on AXHub web
Pick a template, hit Finish, and AxHub handles repo creation through deploy.
The AxHub New app page does it all when you pick a template and hit Finish — it creates a GitHub repo → drops in the template code → connects → deploys. No writing code or creating a repo by hand. Once the app is up, you open that repo in Claude Code and grow it.
You don't set visibility here. A new app starts private (only you can see it); sharing it with your company happens later in Access management.
What you need
- AxHub account — ask your company's
tenant_adminfor an invite - GitHub account — one that can install the axhub GitHub App (a user or org)
Enter the basics
Apps menu → New app. The first block, Basics, has three fields.
Start with the app name and AxHub fills in the subdomain and slug from it. Edit any field if you like.
| Field | What it is | Rules |
|---|---|---|
| App name | The display name your colleagues recognize | 1–100 chars, any language |
| Subdomain | The app's address — becomes {subdomain}.{company}.axhub.ai | lowercase letters, digits, hyphens; 2–32 chars |
| Slug | The key that identifies the app in your company — used in URLs and admin screens | lowercase letters, digits, hyphens; 2–64 chars |
If you type the app name in a non-Latin script (e.g. Korean), the subdomain and slug won't auto-fill — enter those two yourself in lowercase Latin. (e.g. name 내 할일 → subdomain and slug my-todo)
Pick a template
Choose a starter template. Its code goes straight into your new repo, so you start with a working app, not a blank screen.
| Template | Best for | Pod spec |
|---|---|---|
| Vite + React SPA | A static React app — the fastest start. Client-side only, but can call external APIs | S |
| Next.js App Router | Full-stack React with SSR — server components and server actions | M |
| Astro | Content sites and blogs — static-first, dynamic only where needed (islands) | M |
Unsure which to pick — for a web app that needs a screen plus a server, start with Next.js App Router; for a lightweight single-screen UI, Vite + React SPA is a safe bet.
What's a Pod spec? — The Pod spec shown on each template card is the CPU and memory the app gets. The Pod 사양이란? (What's a Pod spec?) button on screen opens the table below. Each template has a recommended default (M), and you can change it after creating the app, in settings.
| Spec | For | CPU | Memory |
|---|---|---|---|
| S · Small | Light workloads | 250m ~ 1000m | 384Mi ~ 768Mi |
| M · Medium (default) | Standard | 500m ~ 2000m | 768Mi ~ 1536Mi |
| L · Large | High-traffic apps | 1000m ~ 3000m | 1536Mi ~ 2560Mi |
| XL · XLarge | Heavy load only | 2000m ~ 4000m | 3Gi ~ 5Gi |
Don't worry if the numbers look unfamiliar: 1000m is one CPU, and Mi/Gi are memory units. The default M is fine for most apps — bump it up later if the app feels slow.
Connect a Git repo
Install the GitHub App (once)
Name the repo
If a repo with that name already exists, it fails (repo_exists). Try a different name.
Finish — deploy in one step
Hit Finish and a progress view appears, running automatically through:
create app → create repo → add template code → connect → deployWhen it's done you land on the In progress tab and get an app URL. Open it to see the template running.
Develop the app
Now open the created repo in Claude Code and add features. The repo is already set up for AxHub (port, structure).
Add [feature] to this AxHub app.
- Read secrets from env vars (process.env), not from code
- On the server, read the logged-in user from X-AxHub-User-ID and X-AxHub-App-Role headersPush your changes to GitHub and a deploy starts again. Secrets, headers, the SDK, and redeploys are covered in Develop the app.