Pre-release software
Entigra is under active development. Features, workflows, interfaces, and project formats may change between beta releases.
BETA INFORMATION & PUBLIC NOTICES
Know what to expect.
This page is the public home for Entigra's beta guidance, privacy commitments, support information, and legal resources. Some policies remain in draft while the beta systems are finalized.
BEFORE YOU JOIN THE BETA
Use copies and backups
Test with copies of important documents and keep independent backups. Beta software should not be the only location for irreplaceable work.
Invitation-based access
Applications are reviewed to build a useful mix of experience levels, workflows, devices, and testing goals.
Private tester access
Approved testers receive access instructions by email and a private Discord invitation verified against the approved email address.
BETA FAQ
Privacy and bug reports
These are the current design commitments. Exact file names, layouts, and diagnostic fields may change before the beta reporting system is finalized.
Are bug reports anonymous?
Planned bug reports are anonymous by default. A tester may choose to include a beta identity or contact information when follow-up would be useful.
What information is shared with a bug report?
Every report will include the tester's written description and basic report context such as the Entigra version, category, and time. Before submission, Entigra is planned to show a readable summary of the information and attachments selected for sharing.
Can I include additional technical information?
Yes. Testers may optionally include selected logs, system details, screenshots, project files, or a system diagnostic report when those materials could help reproduce a problem. Optional material should be visible and reviewable before it is attached.
Will Entigra silently upload my files?
No. Entigra is being designed so projects, screenshots, logs, and diagnostics are not silently attached. The tester decides what leaves the computer.
Will the technical report be readable?
The planned report preview will translate technical metadata into a human-readable view so testers can understand the main information being shared without needing to interpret raw structured data.
Is system diagnostic information required?
No. Additional system diagnostics are optional. They may be useful for graphics, driver, display, or hardware-specific problems, but they are not required for ordinary feedback.
Do I need to write a perfect bug report?
No. A clear description of what you were doing, what happened, and what you expected is valuable. Entigra's beta is intended for real users and real workflows, not only professional software testers.
BETA PROGRAM
Program documents
Beta Participation Terms
Eligibility, access approval, tester conduct, feedback, confidentiality where applicable, version support, account revocation, and the limits of pre-release software.
Known Issues & Release Notes
Current limitations, supported workflows, fixed issues, release channels, and upgrade guidance for each beta build.
Contact & Beta Support
For beta and waitlist questions, email beta@entigrastudio.com. Private Discord access will be shared with approved testers.
LEGAL & PUBLIC POLICIES
Public notices
Privacy Policy
How website inquiries, update signups, waitlist applications, beta reports, optional diagnostics, and account information are collected, used, retained, and deleted. Update and waitlist submissions are transmitted directly to Entigra by the website forms.
Copyright & Intellectual Property Policy
Ownership of Entigra software and branding, user ownership of created work, acceptable use, and procedures for copyright complaints.
Accessibility Statement
Accessibility goals, known limitations, supported feedback channels, and Entigra's approach to inclusive design.
Security & Responsible Disclosure
How to report vulnerabilities safely and what information security researchers should include.