> ## Documentation Index
> Fetch the complete documentation index at: https://docs.major.build/llms.txt
> Use this file to discover all available pages before exploring further.

# What is Major?

> Build, deploy, and share internal tools faster with AI-powered development and secure resource access.

Major is an AI-powered platform for building and deploying internal tools. It combines a live code editor with integrated AI assistance, secure resource management, and one-command deployments.

## What Major does for you

<CardGroup cols={2}>
  <Card title="Deploy instantly" icon="rocket">
    Ship internal tools in seconds. No infrastructure setup, no CI/CD pipelines to configure.
  </Card>

  <Card title="Secure connector access" icon="shield-check">
    Access databases and APIs without managing secrets. Credentials never touch your code.
  </Card>

  <Card title="Build with AI" icon="sparkles">
    Get AI assistance that understands your entire codebase and can implement features directly.
  </Card>

  <Card title="Control access" icon="users">
    Manage who can view, edit, and deploy each app with built-in RBAC.
  </Card>
</CardGroup>

## How Major is different

### No secrets in your code

Traditional development requires managing `.env` files, rotating credentials, and hoping nobody commits secrets to git. Major eliminates this entirely.

Connectors (databases, APIs, storage) are configured once in the dashboard. Your code uses generated clients that authenticate automatically through the Major platform. The same code works locally, in the web editor, and in production.

```typescript theme={null}
// No connection strings, no API keys, no .env files
import { myDatabaseClient } from './clients';

const result = await myDatabaseClient.invoke(
  'SELECT * FROM users WHERE id = $1',
  [userId],
  'fetch-user'
);
```

### AI that understands your code

The Major editor includes an AI assistant with full context of your application. It can:

* Explain complex logic in your codebase
* Implement new features by writing code directly
* Refactor components while maintaining existing patterns

### Unified experience everywhere

Whether you're developing locally with the CLI or in the browser with the web editor, the experience is consistent:

* Same resource access
* Same deployment commands
* Same version control (every app is backed by GitHub)

## Choose your workflow

Major supports two development paths. Pick the one that fits your style:

<CardGroup cols={2}>
  <Card title="CLI Workflow" icon="terminal" href="/getting-started/quickstart-cli">
    Develop in your local IDE with full control. Use `major app start` to run locally and `major app deploy` to ship.
  </Card>

  <Card title="Web Dashboard" icon="browser" href="/getting-started/quickstart-web">
    Build entirely in the browser with the live editor. Get AI assistance and deploy with a single click.
  </Card>
</CardGroup>

Both workflows use the same underlying platform. You can switch between them anytime or use them together.

## Next steps

<CardGroup cols={2}>
  <Card title="Core Concepts" icon="book" href="/getting-started/core-concepts">
    Learn about Apps, Connectors, RBAC, and Environments.
  </Card>

  <Card title="Get Started" icon="play" href="/getting-started/quickstart-cli">
    Jump into building your first app.
  </Card>
</CardGroup>