Using ET: worked scenarios
IT and procurement scenarios
Adoption by an organisation.
Status labels: Live (checked directly, dated) Built in code; not independently verified In progress Planned, not shipped Open decision or unverified Not offered / no claim made
C0182 I am an IT manager. What should I check before a pilot?
The platform limits, disk space, sign-in method, unsigned build, network hosts and the absence of audits. Our IT review page lists them with honest gaps.
C0183 Our security team wants a formal attestation report before approving software. Can you provide one?
No. No SOC 2 exists and we claim none. If it is a hard requirement, ET does not meet it today.
C0184 We need a vendor risk questionnaire answered. Can you?
We will answer honestly, including "not documented", but many answers will be no. Send it through the access page.
C0185 Our legal team needs a data protection agreement. Can we have one?
No DPA exists, and no approved privacy policy exists yet.
C0186 We need SSO. Can ET support it?
Not today. Sign-in uses Google or a MiniStudios account.
C0187 We need to deploy to 50 machines. How?
No enterprise deployment tooling exists. Each install is an 18.2 GB portable extraction, so plan distribution yourself and ask us first.
C0188 We need a proxy allow-list. What hosts does ET use?
The MiniStudios account host for the session check and a public media host for pictures. We found no other network dependency, but have not run an independent trace.
C0189 We need an offline install for an air-gapped lab. Possible?
Sign-in needs a network and we have not verified full offline use, so we cannot say yes.
C0190 We need to restrict which features staff can use. Possible?
Only the hat gate is documented. Role-based feature restriction is not offered.
C0191 We need audit logs. Does ET have them?
No user audit log is offered. The Audit tool on the rail is not described as a compliance log.