You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Drop the roadmap (not actively being worked on) and the community
links (Issues, Discussions, Discord) which are premature for the
current state of the repo.
Copy file name to clipboardExpand all lines: README.md
-24Lines changed: 0 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -413,30 +413,6 @@ We think of English as an API. Managers communicate through natural-language int
413
413
414
414
---
415
415
416
-
## Roadmap
417
-
418
-
Current priorities (roughly in order):
419
-
420
-
-[ ]**Local persistence layer** β lightweight local mode for the `unify` SDK backed by SQLite or Postgres, removing the hosted backend requirement for the core loop
421
-
-[ ]**Local deployment** β `docker compose up` for the full system (brain + persistence + communication) on your machine
422
-
-[ ]**Managed/local convergence** β narrow the remaining gap between the managed Pub/Sub path and the local ingress path
423
-
-[ ]**Broader local provider coverage** β expand turnkey local channel setup beyond the current Twilio/LiveKit/IMAP/SMTP path
424
-
-[ ]**Local storage** β filesystem or S3-compatible alternative to GCS signed URLs
425
-
-[ ]**One-command onboarding** β guided setup that provisions API keys, configures channels, and starts the assistant
426
-
427
-
The long-term goal is a fully self-hosted path with zero external dependencies. Contributions toward any of these are welcome β especially the local persistence layer, which would unlock everything else.
428
-
429
-
Follow [GitHub Issues](https://github.com/unifyai/unity/issues) for detailed progress.
0 commit comments