# Your servers, your models, your data

> OrgKeep is sold as source code, not as SaaS. Your developers can clone the repository, run one command and have it in production without contacting us.

Source: https://orgkeep.com/self-hosted

## What does no lock-in mean in practice?

Every design decision is checked against one test: could your developer run OrgKeep in production with nothing but the repository?

| Area | How OrgKeep does it |
|---|---|
| Install | Docker Compose on any Linux server, on-premises or in any cloud, with Tecfy Tasks as one of its services |
| Database | PostgreSQL with a documented schema, so your own reporting tools can connect |
| Files | Local disk or any S3-compatible storage |
| Email | Plain SMTP |
| Sign-in | Built-in accounts plus OIDC, SAML and LDAP (Active Directory, Entra ID, Google Workspace) |
| AI models | Any provider through the model gateway, including local models |
| Data | Full export, a documented REST API and webhooks |
| Control | No license server, no phone-home, no obfuscated code. Telemetry is off by default |

## How do you install OrgKeep?

Installation is designed around one command:

1. Clone the repository you receive with your license.
2. Copy the example settings and set your domain, database password and email server.
3. Run `docker compose up -d`.
4. Sign in, add your AI providers and create your first AI employee.

```
git clone git@git.example.com:it/orgkeep.git
cd orgkeep && docker compose up -d
```

## Which AI models can you use?

Any of them. You bring your own API keys and choose a provider per AI employee: a small, cheap model for sorting work and a strong one for analysis.

- Hosted providers such as OpenAI, Anthropic, Google and Mistral.
- Local models through **Ollama** or **vLLM**, for organizations where no data may leave the building.
- Tools use **MCP**, the open standard for connecting AI to tools, so you can connect your own systems.

The agent logic lives in OrgKeep's own code, never in a vendor's hosted agent platform that keeps your conversations on its servers.

## What is OrgKeep built with?

| Part | Choice |
|---|---|
| Backend | Go |
| Database | PostgreSQL, with pgvector for search |
| Cache and messaging | Redis |
| Web app | Next.js |
| Install | Docker Compose |
| Task tool | Tecfy Tasks, as its own service in the same install |

> This is the current plan for the first release and may still change.

## Can you change the code?

Yes, within your licensed organization. Common changes are settings, not code: custom fields, roles, approval workflows, branding, languages and email templates. Code changes go in a plugins folder with events and hooks, so your code stays outside the core and updates keep merging cleanly.

Updates ship like a library: tagged releases with a changelog, database migrations and upgrade notes.

## Which languages are included?

English, French and Arabic from day one, with a full right-to-left layout for Arabic. Each person picks their language, and user content such as task titles keeps its own direction. Dates and numbers follow the language, with Western or Arabic-Indic digits.

## Questions people ask

### Does OrgKeep need an internet connection?

Not for its core. With local models and self-hosted sign-in it can run with no outside connection. Connectors to outside services such as Slack or QuickBooks need to reach those services.

### What happens if we stop paying for updates?

You keep the code and keep running it. The updates subscription brings new releases and support; the software doesn't stop working without it.

### Can our developers review the code?

Yes. Code quality is part of what you buy: tests, CI, architecture docs and a one-command developer setup are part of the product, and your developers can review them while you evaluate OrgKeep.