Question 1

What is Nodestitch?

Accepted Answer

Nodestitch is an AI-run operations workspace for privacy-conscious US K–12 technology teams. It turns operational threads into an accountable queue so teams can see the owner, context, and next action without putting student records into the workspace.

Question 2

What operational work does Nodestitch support?

Accepted Answer

Nodestitch supports device and inventory drift, renewals, vendor follow-up, staff requests, audits, support documentation, and exception-oriented follow-up. The focus is operational context and the next decision, not student information.

Question 3

Does Nodestitch store student records?

Accepted Answer

No. Student records are not stored in the workspace. Teams should not submit student names, identifiers, grades, class or roster information, contact details, or other student-record content.

Question 4

What happens if student-record content is submitted?

Accepted Answer

Screening happens before entry or persistence. Blocked values are not echoed, stored, shown in previews, or added to audit payloads. Submit operational context instead, such as a device issue, renewal decision, vendor follow-up, or staff request without student data.

Question 5

What information is appropriate for a pilot or support request?

Accepted Answer

Share a work email, your role or title, your school or district, and the operational challenge you want to discuss. Do not include student data. Start a conversation at /pilot.

Question 6

Is Nodestitch a FERPA certification or legal-compliance claim?

Accepted Answer

No. A pilot defines an operational boundary; it is not a claim of legal compliance or a security certification. Each school or district must complete its own legal, privacy, and security review.

Question 7

Does Nodestitch connect to Google Workspace Admin, Jamf Pro, or Apple School Manager?

Accepted Answer

The public site does not confirm active connectors to Google Workspace Admin, Jamf Pro, Apple School Manager, or any other external admin console. References to systems a team already uses are context, not proof of a connected integration. Contact us at /pilot for current scope rather than assuming connector availability.