| Business benefitsAI-assisted custom feature development Depends on needs Editor versus custom applicationGoogle Sites offers layouts and embeds. Check whether those tools or managed custom functionality fit the job; neither is universally more flexible. | We use AI-assisted engineering for rapid iteration on scoped custom features. This site's API library and interactive comparisons demonstrate delivered application changes. Delivery time depends on scope; no measured competitor speed comparison is claimed. | Layouts and embedded HTML/JavaScript or web apps allow additions. Embedded code does not give full control over the host application. |
|---|
| Direct API integrations Depends on needs Embedded app versus integrated applicationSites can embed an Apps Script web app; WSD implements its API feed inside the application. Different integration paths alone do not establish a better business outcome. Official documentation → | Server-side YouTube API integration is implemented here. PostgreSQL, Supabase and Deno Edge Functions are repository-confirmed; additional integrations are separately scoped. | Apps Script web apps can be embedded. API integration lives in the separate app and requires its own access controls. |
|---|
| Proprietary Spur Machine technology Fleet rollout pending Existing Machines; centralized rollout pendingEstablished Spur Machine research and content production is being brought into the new central Fleet. This Pending label applies specifically to that central platform's hosted rollout. | Western Software has operated proprietary Spur Machines for AI-powered research and content production across multiple business websites. That existing technology is now being consolidated into Spur Fleet; the new centralized hosted rollout is being prepared separately. | Workspace or external applications can supply automation through embeds; it is separate from the page editor itself. |
|---|
| AI-powered research and knowledge production Fleet rollout pending Centralized research and QA rollout pendingSpur Machine research/content production has an existing operating history. The new centralized Fleet research and independent-QA workflow has separate activation requirements; its hosted rollout remains pending. | Our existing Spur Machine operating history covers AI research and content production. The centralized Fleet engine adds source research, AI writing and independent factual/editorial QA before private review; that new hosted workflow is still being prepared. | Good for organizing documents and information. Independent research and publishing review require a separate process. |
|---|
| Organic Search discovery specialization Depends on needs Check required search controlsWSD demonstrates route metadata, canonicals and structured data. Verify the exact Sites controls and public content before calling them equivalent or awarding an advantage. | Our managed website work emphasizes clear business information, server-rendered content, metadata, canonicals, internal links and a sitemap. The Academy explains our research-led approach. Search results require useful content and measurement; rankings are not guaranteed. | Public publishing is available, but editor-level controls differ from a custom site's route metadata and structured data. Review requirements before choosing. |
|---|
| AI Search discovery specialization Depends on needs Eligibility, not citationsHelpful, accessible content matters across platforms. Neither architecture nor AI tooling guarantees answer inclusion. | We specialize in organizing clear, crawlable, source-supported business knowledge for AI-assisted discovery, following Google's published guidance. This is an engineering and content approach, not a guarantee of AI mentions or citations. | Public access and crawlable information must be checked. Embedded or access-restricted documents are not a substitute for indexable page content. |
|---|
| Managed engineering and business fit Google Sites advantage Google document sharingGoogle Sites includes Google file and content embeds for lightweight information sharing. WSD is not a demonstrated replacement for that ready-made Workspace-oriented workflow. Official documentation → | WSD builds, maintains, improves and manages business websites according to the purchased package. Custom features and direct integrations are scoped to business needs. Established Spur Machine technology and the new centralized Fleet rollout have distinct implementation stages. | Google Sites advantage Team portals, project information and lightweight public sites, especially when Google Workspace collaboration is the priority. |
|---|
| Technical trade-offsEditors, plugins and prebuilt features Depends on needs Different editing and dependency choicesCMS apps, application libraries and hosted services all need an owner. Fewer plugins is not evidence of fewer risks. | Direct application features rather than a CMS plugin layer. React libraries, hosting and external services remain real dependencies. | Built-in Google content and external embeds are useful but retain their own availability and permission dependencies. |
|---|
| Website architecture Depends on needs Different operating modelsChoose a managed application or a publishing/editor platform around your workflow. The architecture alone does not establish a winner. | Custom React and TypeScript application with server-rendered public pages, Tailwind CSS and purpose-built components. | Google-hosted page editor that assembles text, media, documents and embedded content. |
|---|
| Performance and page speed Not verified No measured speed comparisonNo matched real-page benchmarks are available. Implementation, content and hosting determine speed. | Control over rendering, assets and caching enables targeted optimization. Actual speed needs measurement; custom code is not automatically faster. | Delivery is hosted; embedded resources may add loading work. Evaluate public pages and their embeds on real devices. |
|---|
| Security and maintenance Not verified No security rankingDifferent maintenance responsibilities do not prove stronger security. Both need access controls and responsible updates. | Server-side secrets, controlled access and tested changes are demonstrated here. Application dependencies and hosting still need ongoing security work. | Google manages hosting, while sharing permissions and embedded app authentication determine who can see information. |
|---|
| Scalability Not verified Capacity needs validationNo equivalent workload tests establish a winner. Assess content volume, service limits and operating costs. | Application architecture can evolve around workload and data needs. Capacity, provider limits and operating costs must be validated for each project. | Convenient for information sharing; custom application and data workloads belong to external services, with their own limits. |
|---|
| Ongoing technical maintenance Depends on needs Different maintenance responsibilitiesHosted platforms and managed custom applications both need ongoing care. Compare the actual support scope and connected services. | Managed operations follow the purchased package. Custom software needs testing, dependency updates and integration maintenance; it is not maintenance-free. | Maintain sharing rules, embeds and links. Embedded apps have their own operating and authorization requirements. |
|---|
| Website portability and ownership Depends on needs Migration and contract dependentContent exports, application source and working backends are different assets. Verify handover rights and what survives a move. | Code is version-controlled, not locked to a theme editor. Source access, IP ownership and handover are contractual; moving hosting or data requires planning. | Content can be retained or exported through Google tools. Data export is not the same as a fully independent application deployment. |
|---|