An unresolved question and a workflow you know well. Do not send records with the application.
Help shape a more rigorous genealogy research workspace.
Private beta applications are open. Invitations have not started; hosted access begins only after the launch gates pass. We’re prioritizing family historians and genealogists with rigorous source, GEDCOM, and case workflows—and the patience to give detailed feedback.
Applying does not create an account, accept participation terms, or authorize family-data submission.A strong fit
You have a research process to test—not just a feature list.
Private beta applications are open. Invitations have not started; hosted access begins only after the launch gates pass. Applying does not guarantee access.
Living people and sensitive data. The application itself should contain no family records.
Proposed cohort-one contract
Small by design, with the difficult boundaries stated upfront.
These are the intended launch limits, pending owner approval, counsel-reviewed documents, and recorded operational evidence.
Proposed to include
- An invitation-only private archive for one researcher or trusted household
- Reviewable plain-GEDCOM import, apply, rollback, and full GEDCOM export
- People, sources, cases, evidence, hypotheses, tasks, and deterministic checks
- A read-only, owner-scoped API preview only after its separate gate passes
Excluded
- DNA files or match triage
- External-provider AI
- Binary source images, ZIPs, or media packages
- Real-data public publishing, open signup, billing, or shared multi-family hosting
Operating boundary
- Synthetic records first; real data only after every applicable gate
- One isolated real-data cell, not a shared multi-tenant service
- Operator-assisted export and deletion
- No uptime SLA or guarantee of zero data loss
From application to archive
An application is not an invitation—and an invitation is not permission to skip the gates.
- Apply without recordsSend only the fixed contact and workflow fields shown below. There is no free-text field or file upload.
- Private selectionA founder reviews fit and capacity. There is no automatic account creation or guaranteed placement.
- Review exact documentsBefore account creation, an invite presents the approved participation terms, privacy notice, and cohort boundary for explicit acceptance.
- Start syntheticUse fictional Hartwell–Mercer data first. Real family data remains prohibited until every real-data gate is approved and evidenced.
Beta interest
Tell us about the work you want to test.
The fallback intake opens a prepared email addressed to beta@kinresolve.com. The marketing site does not store your submission.
Submitting consents only to beta communications. It does not accept participation terms or authorize Kin Resolve to receive family records. Read the current data-practices disclosure before applying.
Please do not submitGEDCOM files, DNA results, relatives’ or other living people’s names or details, source images, credentials, or private family details.
beta@kinresolve.com is for applications and cohort communication. Participant support will use support@kinresolve.com; private vulnerability reports will use security@kinresolve.com. The support and security routes must be delivery-tested before invitations begin.
Do not email family records, GEDCOM files, screenshots of private research, credentials, API tokens, or genetic information. A private transfer route must be arranged if evidence bytes are genuinely necessary.
Questions before applying
Small cohorts, clear boundaries.
Is the beta free?
The proposed first 30-day pilot is free and has no billing or payment-information step. The invitation states the exact participation terms before an account is created.
When will I get access?
Invitations have not started. Applying records interest but does not create an account, guarantee access, or place you in an automatic queue. Cohorts will remain deliberately small after the launch gates pass.
What file can the proposed pilot accept?
Plain .ged or .gedcom only, initially limited to 10 MiB (10,485,760 bytes) and 40,000 people. Source work is limited to metadata, links, and pasted text or transcripts.
Can I upload family data?
Not when applying. Every participant starts with synthetic records. One isolated plain-GEDCOM pilot may accept real family data only after the legal, restore, deletion, recovery, and security gates pass.
Can I use DNA, external AI, media, or public publishing?
No. DNA, external-provider AI, binary source attachments, media packages, and real-data public publishing are disabled for cohort one.
What support is proposed?
Founder-operated onboarding and a one-business-day support acknowledgement target, with weekly check-ins and announced maintenance. This is a target, not an uptime or response-time SLA.
What am I agreeing to when I apply?
Only to receive beta communications. Applying is not acceptance of beta participation terms. An invitation can be accepted only after the approved participation terms, privacy notice, and cohort boundary are published and presented for explicit acceptance.
Can I self-host?
The AGPL source is available now. The current Compose path is suitable for development and beta evaluation while production hardening continues.