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 |
| 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:
- Clone the repository you receive with your license.
- Copy the example settings and set your domain, database password and email server.
- Run
docker compose up -d. - 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 -dWhich 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.