Elembra
Open-source sovereign business memory workspace for durable team knowledge, files, notes, Chat, and permission-aware AI workflows.
Elembra's target architecture is a small Platform Core with independently owned Files, Notes, Mail,
Chat (powered by Buzz), Memory and Agents Applications. See the platform architecture.
The accepted institutional architecture
retains tenant isolation while deferring independent collaboration workspaces; current workspace
fields are compatibility aliases and do not provide workspace membership administration.
The GitHub repository is still named rustshare; Elembra is the current product and architecture name.
[!NOTE]
RustShare is currently in Public Preview: early, actively evolving, and not yet intended for production use. Feedback, testing, and first contributions are welcome.
Getting Started • Community • Deployment
Public Preview Status
RustShare is currently in Public Preview. The codebase is early, actively evolving, and open for feedback, testing, beta users, and first contributors.
It should not be treated as finished, production-ready, or enterprise-ready yet.
Current focus
RustShare currently exists as an MVP and is being refined toward a stronger production design. The current work focuses on:
- polishing the existing implementation instead of rewriting blindly
- identifying gaps between the MVP and the intended product direction
- enforcing clearer architecture and behavior contracts
- converging on a secure, multi-tenant, integration-friendly design
How to Report Useful Feedback
The fastest way to help us improve RustShare is to report what you actually tried and what happened.
A useful bug report or feedback item usually includes:
- What you were trying to do — the task, feature, or workflow you were exploring
- What happened instead — the error, unexpected behavior, or missing capability you saw
- What you expected to happen — the behavior or result you were hoping for
- Operating system and setup method — for example, Docker Compose, local dev build, or the macOS desktop CLI
- Safe error messages — logs, stack traces, or screenshots are welcome, but please remove passwords, tokens, private URLs, customer data, and other sensitive values first
For questions and general support, see SUPPORT.md. For development setup and contribution guidelines, see CONTRIBUTING.md. For contributor and AI-agent workflow guidance, see AGENTS.md and docs/agent-guides/.
Security and Sensitive Data
Please do not post passwords, access tokens, private URLs, customer data, confidential logs, or other sensitive information in public GitHub issues.
If you believe you found a security problem, please see SECURITY.md to report it privately.
What this is
RustShare is a durable memory and artifact layer for technical teams that need control over their documents, files, notes, diagrams, and long-lived operational knowledge.
It focuses on:
- durable company memory
- files, notes, diagrams, and technical artifacts
- markdown-based knowledge work
- meeting notes and decision records
- self-hosted deployment
- audit-friendly artifact storage
- API-driven integrations
- future permission-aware AI memory foundations
What this is not
RustShare is not positioned as a Dropbox clone, a Nextcloud clone, or a generic file-sharing app.
It is not presented as a fully mature enterprise content platform yet. It is a public-preview infrastructure product for teams that are comfortable evaluating and operating self-hosted software.
Getting Started
First-use Elembra installation
For a clean Elembra installation using published, immutable release images,
follow the Customer Alpha Operations Runbook.
It initializes the deployment with ./scripts/elembra.sh, applies the clean
database baseline, and provisions bundled Chat. The source-build quickstart
below is for local development, not the supported first-use deployment.
Local development quickstart (Docker Compose)
git clone https://github.com/kubedoio/rustshare.git
cd rustshare
cp .env.example .env
# REQUIRED: .env.example ships with empty secrets and the backend refuses to
# start without them. Generate strong secrets (this edits .env in place):
./scripts/pre-flight.sh
docker compose up -d
The first build compiles both the frontend and the backend, so it can take several minutes. Wait for the backend container to become healthy (docker compose ps), then visit http://localhost.
This Docker Compose quickstart has been validated on Ubuntu 22.04 LTS, Ubuntu
24.04 LTS, and Debian 12.
Admin password — record it immediately. Unless you set RUSTSHARE_ADMIN_PASSWORD in .env before first start, the backend generates a random admin password ONCE at first boot and writes it to a bootstrap file inside the backend container. Retrieve it right away:
scripts/read-bootstrap-password.sh "$(docker compose ps -q backend)"
The bootstrap file lives in container-local storage and does not survive container recreation — after docker compose down / --force-recreate, an unrecorded auto-generated password is unrecoverable. For a durable credential, set RUSTSHARE_ADMIN_PASSWORD in .env before the first docker compose up -d (an empty value is treated as unset and triggers auto-generation).
This is the beginning of the README. Read the rest at the original. Read the full README ↗
