Skip to content

COMMUNITY_LAUNCH.md

Latest commit

 

History

History
191 lines (130 loc) · 7.46 KB

COMMUNITY_LAUNCH.md

File metadata and controls

191 lines (130 loc) · 7.46 KB
Raw

EleSync Community Launch

This guide is for sharing EleSync with communities that already understand the problem of repeating context across AI assistants.

The simple message

I built the missing memory layer because I was tired of starting from zero with every AI assistant.

EleSync is your private AI workspace. It lets your AI assistants share memory, knowledge, and project context while keeping your data under your control.

Do not lead with a list of internal components such as vault, MCP, PWA, knowledge base, or AI team. Those are proof points under the main idea.

Who to reach first

Prioritize communities where the problem is already visible:

  1. Local AI communities — people running Ollama, local models, desktop assistants, and private workflows.
  2. Open-source AI communities — people who value inspectable, portable, user-owned tools.
  3. MCP communities — people looking for practical servers and real client workflows.
  4. Developers frustrated by AI context limits — people repeating project background across ChatGPT, Claude, Gemini, Grok, and coding assistants.
  5. Privacy and self-hosting communities — people who want useful AI without making a hosted account the center of their workflow.

Start with a few relevant communities and participate before posting a launch announcement. Answer questions, show the workflow, and invite criticism.

The five-minute demo

The strongest demonstration is not a feature tour. It is one complete result:

  1. Install EleSync.
  2. Choose a local vault.
  3. Import a small, non-sensitive AI export.
  4. Show the imported memories in the dashboard.
  5. Create a project.
  6. Add one knowledge sheet or decision.
  7. Connect one assistant.
  8. Ask the assistant what it knows about the project.
  9. Switch assistants or continue the work without repeating the background.

Keep the demo small. A real project with three useful memories is better than a large empty feature tour.

Launch post template

I built the missing memory layer because I was tired of starting from zero with every AI assistant.

EleSync is a local-first private AI workspace. It keeps the memory, knowledge, tasks, decisions,
and project context that you choose in a vault you control, then lets approved assistants use it.

The first workflow is simple:

1. Import your existing AI history.
2. Create a project.
3. Connect an AI assistant.
4. Ask it to continue with the context you already saved.

The vault is local by default. No mandatory EleSync cloud account is required. Imports can be reviewed
before they become durable knowledge, and project/scoped access limits what an assistant can see.

Current areas:
- ChatGPT, Claude, Gemini, Grok, WhatsApp, and document imports
- Projects with knowledge, tasks, decisions, and handoffs
- MCP connections for local and remote assistants
- Connection Health for setup and troubleshooting
- PWA/mobile capture and offline drafts

I would especially like feedback on the first five minutes:
Can someone who has never seen EleSync understand why it is useful without an explanation from me?

Project: <link>
Demo: <link>
Feedback: <issue/discussion link>

Short versions

One sentence

EleSync is a private local-first workspace that lets your AI assistants share memory, knowledge, and project context.

Problem-first

Every AI assistant forgets the context you already explained somewhere else. EleSync keeps the durable context you choose in a local vault and makes it available to approved assistants.

Developer/MCP version

EleSync is a local-first MCP workspace: import your existing AI history, organize it into projects, and give MCP clients explicit, scoped access to the context they need.

Privacy version

EleSync keeps your vault on your computer by default, does not require a hosted account, supports optional encryption at rest, and lets you control AI access by scope and project.

What to show

Use real, small examples:

  • Import: an anonymized ChatGPT, Claude, Gemini, or WhatsApp export.
  • Dashboard: the memories and sources that were actually imported.
  • Projects: one project with a knowledge sheet, task, decision, and handoff.
  • AI connection: a real local Claude project connection or a verified remote connector.
  • Mobile PWA: capture a short note or shared link from a phone and show it in the vault.
  • Privacy: show the vault path and explain which content was approved for the assistant.

Do not publish private conversations, phone numbers, tokens, tunnel URLs, personal vault paths, or real project secrets in a demo.

Questions to invite

Ask the community:

  • What would you import first?
  • Which AI assistants do you switch between during one project?
  • Would project-scoped access be useful to you?
  • What would make you trust a local AI workspace?
  • Where does the five-minute flow become unclear?
  • Which export format is missing or difficult to review?

The best early feedback is about confusion, trust, and completion—not requests for another large feature.

Honest limitations

State these clearly:

  • Remote AI connections need public HTTPS reachability and provider authorization.
  • Optional encryption is not enabled by default.
  • The computer must be running for live PWA access.
  • A project-bound connection must be used when strict project isolation is required.
  • Provider-specific OAuth behavior depends on the provider's current connector support.
  • The project is in a stabilization phase; reliability and onboarding take priority over feature expansion.

Contribution paths

The most useful community contributions right now are:

  • Reproducing and fixing onboarding or import friction.
  • Testing exports from AI providers outside the core test environments.
  • Testing the five-minute flow on Windows, macOS, and Linux.
  • Testing PWA behavior on real phones.
  • Improving privacy review and redaction coverage.
  • Improving documentation with accurate screenshots and short demos.
  • Reporting misleading states with exact steps and screenshots.
  • Reviewing project isolation and connection behavior.

Avoid opening feature requests for large new subsystems until the current workflow is demonstrably effortless.

Sustainability options

The free local-first core remains compatible with several future models:

Free

  • Local vault
  • Imports
  • Basic MCP
  • Local dashboard
  • Core project organization

Community support

  • Donations
  • GitHub Sponsors
  • Small recurring supporter memberships
  • Documentation and translation sponsorships

Optional paid products later

  • Hosted/team workspace
  • Managed collaboration
  • Enterprise access controls
  • Organization audit and policy tools
  • Managed deployment and support

Paid offerings should fund convenience, collaboration, support, and organizational controls—not take away the local vault or force cloud dependence on individual users.

Launch checklist

Before posting:

  • The README explains the problem in the first screen.
  • The five-minute path works on a fresh install.
  • The demo uses anonymized data.
  • The AI connection is actually verified, not merely configured.
  • The public URL does not expose a token or personal path.
  • The screenshot/GIF shows the current UI.
  • The post says what is stable and what is still experimental.
  • A feedback issue or discussion is ready.
  • Community questions will be answered after launch.

Product anchor

Everything in the community launch should reinforce one sentence:

EleSync gives you a private workspace that your AI tools can share.