Beta Tester Hub

Start safely, test one clear path, and report evidence without sharing private data.

BRUTALIST

Before You Test

Use a copy of an export or synthetic sample data. Keep the original source and a separate backup. Do not test with your only copy, production credentials, confidential records, regulated data, or anything you cannot safely delete. Preview generated files before importing them elsewhere.

What Is Ready to Test

Product Status Best for Tester path
FreENEXt Client-side conversion workbench Testers evaluating reciprocal Markdown and note conversions locally in-browser. Open FreENEXt Workbench
FreeMyData Data Un-siloing Testers extracting tables, databases, and structured archives into portable Markdown. Open FreeMyData
FreeMyRecipes Standalone utility Testers evaluating URL-to-Markdown recipe extraction with all ads stripped out. Open FreeMyRecipes
Additional sources and packaged apps Coming Soon Testers waiting for a source or platform not listed above. Do not submit real data yet.
Federation and community services Blocked / no tester cohort No tester cohort. Not part of portal testing or onboarding. Not part of portal testing or onboarding.
Internal dashboard Out of scope Explicitly excluded from tester access. Not accessible to testers.
Commerce / payment activation Out of scope No checkout, purchasing, or payment instructions are part of this invited release. Not part of tester scope.

Your First Session

FreENxt

Migration Copy

  1. Export a small, non-sensitive sample from a supported source.
  2. Duplicate the export and preserve the untouched original.
  3. Run the conversion and review the estimate or warnings before continuing.
  4. Inspect several Markdown files, attachments, links, and metadata.
  5. Record the build or release shown, source type, item count, and result.
FreeMyRecipes

Recipe Capture

  1. Choose a public recipe page you are allowed to access.
  2. Submit one URL; do not use account-only or private pages.
  3. Confirm the title, ingredients, instructions, source link, and media references.
  4. Save the result as a test copy and note any missing or reordered content.
  5. Record the browser, page URL, time, and visible release or build.
FreeMyData

Data Un-siloing

  1. Choose a sample CSV, Notion database export, or unstructured folder.
  2. Select your target export format in the reciprocal matrix.
  3. Verify that schemas, properties, and relationships map accurately into Markdown frontmatter.
  4. Review the generated completion report and verify offline file integrity.
  5. Record the source format, row/note count, and result.

Expectations and Limits

Known Limitations

  • Only sources and flows named above are in scope.
  • Conversions may reject unsupported pages, exports, or malformed content.
  • Preview interfaces and output formats may change between builds.
  • Hosted sync, packaged mobile apps, and additional import sources are not tester promises.

Privacy and Data Handling

  • Redact names, addresses, account IDs, access tokens, and private content from reports.
  • Attach the smallest synthetic reproducer possible, never an original personal archive.
  • Optional portal analytics remain consent-gated; review the Privacy Policy.
  • Delete test copies when you no longer need them and retain your own backup.

Accessibility

  • Core paths should work with keyboard-only navigation and visible focus.
  • Text should remain usable at 200% zoom without losing actions or content.
  • Controls need meaningful names, status must not rely on color alone, and errors should identify a next step.
  • Report assistive technology, browser, operating system, and the exact blocked task.

Conduct and Support

  • Be specific, respectful, and patient with other testers and maintainers.
  • Do not probe accounts, infrastructure, admin panels, or data that is not yours.
  • Do not publish suspected security or privacy issues; report them privately to [email protected].
  • Beta support is best-effort and does not guarantee recovery, compatibility, or response time.

Report a Result

Use the Bosun PKM Tools issue tracker for ordinary product bugs and feedback. Search for an existing report first. For a suspected security or privacy issue, email [email protected] instead of opening a public issue.

Include this evidence

  • Product name and visible release/build identifier; if none is shown, say "not displayed."
  • Date and time with time zone, operating system, browser or runtime, device type, and viewport when relevant.
  • Smallest reproducible steps, expected result, actual result, and whether it happens again.
  • Sanitized source type and approximate item count; never include private source content or credentials.
  • Redacted screenshot, console message, or output excerpt only when it materially explains the failure.

Tester Access Boundary

Tester access covers only the public product paths linked on this page. It does not grant access to internal dashboards, deployment systems, administrative consoles, moderation tools, federation services, provider accounts, server hosts, credentials, or private repositories. Stop and report privately if a test path unexpectedly exposes any of them.