Turn your cloud storage into a secure, trackable data room.
Coneshare is an open-source, self-hosted platform that adds control, visibility, and workflow automation on top of your existing storage (Nextcloud, Google Drive, Dropbox).
Share documents securely, track engagement in real time, and trigger actions—without moving your files.
Quick Start · Docs · Live Demo · Roadmap · Forum
⭐ If this project is useful, please star the repo.
Coneshare acts as a layer on top of your storage:
- Files stay in your storage (Nextcloud, Google Drive, Dropbox)
- Coneshare adds:
- Secure sharing controls
- Document engagement tracking
- Workflow automation
No migration. No duplication. No vendor lock-in.
Instead of asking “Did they read it?”, you’ll know exactly how your documents are used.
Add secure sharing on top of your storage:
- Password protection, expiration, email verification
- Download restrictions and dynamic watermarking
Understand how documents are used:
- Views, revisits, downloads
- Page-level engagement insights
Turn activity into workflows:
- Slack and webhook integrations
- Real-time notifications and automation
- Self-hosted by design
- Works with your existing storage
- No migration required
Coneshare works with your existing storage:
- Nextcloud (self-hosted)
- Google Drive
- Dropbox
More integrations coming soon.
Know when investors view your deck or data room—and follow up at the right moment.
Track proposal engagement and prioritize high-intent prospects.
Share sensitive documents with full control and visibility.
Run fully self-hosted while maintaining modern sharing workflows.
Coneshare is built for teams who:
- Use cloud or self-hosted storage (Nextcloud, Drive, Dropbox)
- Share sensitive documents externally
- Need visibility into document engagement
- Prefer self-hosted or private infrastructure
Choose your path first:
- Self-hosted deployment (recommended for first-time operators):
- Use coneshare-compose for installation, runtime, and operations.
- Contribute to Coneshare source code:
- Use the local source build flow below.
Run Coneshare locally for development and contribution:
git clone git@github.com:coneshare/coneshare.git
cd coneshare
cp .env.template .env
make build
make up
make migrateAfter make up and make migrate, verify the basics before configuring storage integrations:
- Frontend is reachable at http://localhost:5173
- API responds at http://localhost:8000/api/v1/
- Core services are up (
backend,frontend,core,redis,celery) - Local files are persisted under the project data/storage volumes configured by
docker-compose.yml - Smoke test:
- Upload one document
- Create a share link
- Open that link in a private/incognito window and confirm view access works
.envandSITE_DOMAINmismatch:- Confirm
.envexists (copied from.env.template) andSITE_DOMAINmatches how you access the app locally.
- Confirm
- Backend cannot reach
coreservice:- Check service names/ports in
docker-compose.ymland inspect backend/core logs for connection errors.
- Check service names/ports in
- Redis/Celery issues (background jobs not running):
- Confirm both
redisandcelerycontainers are running; then check Celery worker logs.
- Confirm both
- Local storage path/permission issues:
- Verify mounted storage paths exist and are writable by container processes.
- Where to look first:
- Run
make logsfrom repo root, then focus onbackend,core, andceleryerror lines first.
- Run
Coneshare is a multi-service stack:
backend/: Django + DRF API, Celery, Redis-based async taskscore/: Go file service for secure file I/Ofrontend/: React + Vite web appdocs/: Product and architecture documentation
Technical reference:
Contributions are welcome. Open an issue, start a discussion, or submit a pull request.
- Docs: https://docs.coneshare.com/en/
- Discussions: https://github.com/orgs/coneshare/discussions
- Email: dev@coneshare.com
MIT License. See LICENSE.
For security issues, contact dev@coneshare.com.