Back to Documentation
AMADEV Docs
AmaStudio

AmaStudio Login & Authentication

How to log in to AmaStudio with your amadev.org account, create API keys, and authenticate with the cloud backend.

AmaStudio Login & Authentication

AmaStudio uses amadev.org as its authentication and AI backend. You need an amadev.org account to use cloud features.

Login Flow

Step 1: Open Login Page

Launch AmaStudio. On the Welcome page, select Login with amadev.org.

Step 2: Choose Auth Method

You have two options:

Option A: Credentials Login

  • Enter your amadev.org email and password
  • AmaStudio logs you in and automatically creates an API key
  • The key is stored securely in the app config

Option B: API Key

  • Enter an existing API key (format: amallm_...)
  • Create one at https://amadev.org/admin/apikey
  • Paste the key directly in AmaStudio

Step 3: Connected

Once authenticated, AmaStudio is connected to amadev.org. You can:

  • Chat using amadev.org's AI models
  • Sync knowledge bases
  • Use agent runtime features
  • Access cloud-stored data

Creating an API Key

From amadev.org Admin Panel

  1. Go to https://amadev.org/admin/apikey
  2. Click Create New API Key
  3. Enter a name (e.g., "AmaStudio")
  4. Optionally restrict allowed models and rate limits
  5. Copy the key immediately — it's shown only once

From AmaStudio (after login)

After credentials login, AmaStudio handles key creation automatically.

Managing Your Connection

  • Connected state: Shows in the provider settings as "Connected to amadev.org"
  • Disconnect: Click "Disconnect" in provider settings to remove your API key
  • Switch accounts: Disconnect and re-login with different credentials

Architecture

Code
┌─────────────────┐       ┌─────────────────┐
│   AmaStudio     │──────▶│  amadev.org     │
│   (Electron)    │       │  (Next.js)      │
│                 │◀──────│                 │
│  AmadevService  │       │  /v1/*      │
│  IPC: Amadev_*  │       │  Auth + Proxy   │
└─────────────────┘       └─────────────────┘

AmaStudio uses a hidden BrowserWindow for credential login, then stores the API key securely. All subsequent API calls use X-API-Key or Authorization: Bearer headers.