SiteWright
A managed, tenant-isolated gateway that exposes approved construction and field-service records as read-only tools with scoped authorization, evidence and support.
Construction and field-service teams store projects, budgets, requests, logs and job records across multiple operating systems. SiteWright proposes a managed gateway that maps approved records into a consistent read/query tool surface for AI clients. The supplied research confirms several active competitors and community implementations, including a construction-native product and a maintained commercial project. That corrects the original assumption of a nearly empty category. The remaining angle is verified multi-platform depth, tenant isolation and operational support—not being first.
A platform login, delegated authorization and project permission are different things. A model request is not user intent, and a successful connector response does not prove that the requester may see every returned field. Bid data, subcontractor pricing, customer details, technician locations and internal notes can be commercially sensitive or personal. Read-only reduces mutation risk but does not prevent over-broad retrieval, inference, export or cross-tenant contamination. An audit log records events; it does not by itself establish a security certification or compliance posture.
Platform account, connector grant, tenant membership, project scope, field policy, tool schema, model request, gateway decision, upstream query, source response, filtered result, citation, user-visible answer, export and later business action remain separate. The first release should prove narrow read correctness and revocation across one verified platform before promising a universal endpoint, formal assurance or supported coverage of every named system.
A construction or field-service technology leader responsible for introducing AI assistants while preserving tenant, project and record-level access boundaries across operating systems.
Active products, community builds and a reported platform migration show that the category is forming now.
Construction technology leaders are actionable buyers, though company tier, procurement owner and acceptable budget need validation.
Multiple cross-references and inbound connections support internal coherence, but no supplied cross-vertical cluster grounds a higher score.
The input identifies a technical buyer, concrete construction records, active category demand and a reusable authorization-and-mapping layer across multiple operating systems.
Competition is already active, coverage and assurance claims need direct proof, platform mappings require maintenance, and read-only tools can still expose sensitive data.
Discussion
No comments yet — be the first to weigh in.