| Business benefitsAI-assisted custom feature development Depends on needs Custom features, scoped to the businessWSD demonstrates AI-assisted application engineering. Other platforms can use custom developers and AI tools too; delivery speed depends on the agreed feature and review work. | 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. | Themes, plugins, blocks and custom PHP can provide extensive customization; it is not limited to templates. |
|---|
| Direct API integrations Comparable Direct integration capabilityWordPress offers REST APIs and custom endpoints; WSD demonstrates direct server API integration. Plugins are an option, not a requirement. Official documentation → | Server-side YouTube API integration is implemented here. PostgreSQL, Supabase and Deno Edge Functions are repository-confirmed; additional integrations are separately scoped. | Built-in REST API and custom endpoints allow direct integrations. Plugin-based integrations are common, not mandatory. |
|---|
| 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. | AI features can be added through plugins or custom services. Research quality, review, provider access and cost controls need separate implementation. |
|---|
| 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. | Native posts, pages, taxonomies and editorial workflows support publishing. Independent research and factual QA require an additional process or integration. |
|---|
| Organic Search discovery specialization Comparable SEO foundationsBoth approaches support public content and search-related configuration. This is capability parity, not a ranking or traffic comparison. | 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. | Strong SEO is achievable with well-built themes, useful content and suitable configuration. Plugins can assist; they cannot guarantee rankings. |
|---|
| 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. | Accessible, indexable content can support AI Search eligibility. A theme or AI plugin does not guarantee inclusion in generated answers. |
|---|
| Managed engineering and business fit Depends on needs Choose for the business needA platform is a better fit only for a stated workflow. WSD is not the right choice for every business. | 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. | Content-heavy businesses and editorial teams valuing a familiar CMS, broad ecosystem and control over hosting. Custom application needs can also be met with development. |
|---|
| Technical trade-offsEditors, plugins and prebuilt features WordPress advantage Built-in content editingWordPress supplies a block editor for pages and posts. WSD changes use its managed application workflow; a comparable self-service CMS is not demonstrated. Official documentation → | Direct application features rather than a CMS plugin layer. React libraries, hosting and external services remain real dependencies. | WordPress advantage Plugins often deliver ready-made features. Custom functionality need not rely on off-the-shelf plugins, but every extension has a maintenance owner. |
|---|
| 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. | PHP-based open-source CMS with themes and a content database. Its REST API also supports custom or headless frontends. |
|---|
| 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. | Can perform strongly with suitable hosting, caching, images and disciplined extensions. Test the actual installation rather than the CMS name. |
|---|
| 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. | Core, PHP, themes and plugins require updates and hardening. Managed hosting can take on some of these tasks; permissions and backups still matter. |
|---|
| 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. | Hosting, database tuning, caching and extension choices determine workload capacity. WordPress can serve substantial publishing operations. |
|---|
| 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. | Coordinate core/theme/plugin releases, staging, backups and rollback. A specialist can provide managed operations, just as a custom application needs an operator. |
|---|
| 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. | Open-source code and a choice of hosts support portability. Content export is available; themes, files and full database migration need separate handling. |
|---|