Account setup
Sign in, connect GitHub, configure billing, and invite teammates.
Appentic accounts are tied to your Google identity, so there are no separate passwords to manage and no extra signup flow. Signing in with Google both creates the account and authenticates you.
Sign in
Visit app.appentic.com and click Sign in with Google. Pick the Google account you want to use for Appentic. On first sign-in, Appentic creates a default workspace for you so you can start deploying immediately.
If you work across multiple Google accounts (say, a personal one and a work one), sign in with whichever you want this Appentic account tied to. You can invite your other addresses as workspace members later.
Connect GitHub
To deploy from a repository, you need to install the Appentic GitHub App on the organisations or accounts that own the repos. From the dashboard, open Settings → Integrations → GitHub and click Install.
GitHub will ask which account or organisation to install on, and whether to grant access to all current and future repositories or a specific subset. Either is fine, and you can change it later from GitHub's own Integrations settings page without reinstalling the app.
The Appentic GitHub App only reads metadata and listens for push webhooks on repos you've granted it access to. It never reads private repositories outside the scope you chose.
Set up billing
Appentic is usage-based. You can explore the platform and deploy small services on free signup credit, but to run workloads beyond the free tier you need a payment method on file.
From Settings → Billing, add a card. The billing page also shows your current credit balance, month-to-date usage, and invoice history, so you can see what you're spending before the end of the cycle.
See Billing for how usage is metered and Credits for how prepaid credits are applied.
Invite teammates
Workspaces are shared. Anyone you invite can see and operate every service and resource inside them. From Settings → Members, click Invite and enter your teammate's email. They'll receive a link to join, and once they accept they'll land directly in your workspace.
If you need finer-grained access than "everyone sees everything" (say, production isolation), put those services in a separate workspace with its own member list.