Intakit Sites
Keep the website you have or move it to Intakit. Either way, the public journey connects to protected intake, attribution, approved publishing, search visibility, and AI discovery—without exposing private legal work.
Modernize the front door without gambling the authority behind it.
Keep the existing CMS or agency-managed site as the live source of truth. Connected Foundation includes protected intake and portal links, attribution receipt, and endpoint monitoring; Authority Review-led remediation, delivery, and connectors activate only when proven for the firm’s CMS.
Move the public website to a separately deployed public-only Intakit runtime that preserves the governed web estate, removes the public WordPress/plugin stack, adds machine-readable authority, and hands visitors securely to the protected firm workspace.
A canonical public answer earns a visit. Intakit preserves attribution through the inquiry and secure intake, learns from the resulting matter, routes approved insight back into governed publishing, and verifies the live URL without exposing private case data to the website runtime.
The point is not React instead of WordPress. It is moving the firm’s public authority onto an isolated, measurable foundation without disconnecting it from intake and firm intelligence.
The current website stays live while Intakit builds and proves the replacement beside it. An unexplained route difference, broken protected journey, analytics failure, or unrehearsed rollback keeps launch blocked.
Albaugh staging proof · July 10, 2026
The exact QA-host browser gate found zero failed redirects, unresolved internal links, or failed public assets and measured 100% minimum normalized coverage of the imported governed body corpus. This is staging evidence for the governed corpus—not a ranking guarantee or the final customer-domain launch certificate.
Controlled early access: Native Sites is in controlled release with Albaugh as the first proof migration. The isolated runtime and evidence system are proven on the QA domain; a customer-domain launch is accepted only when that customer’s route, security, analytics, and rollback packet is green.
Migration pricing is based on canonical content routes, not generated archives or governed redirects. The signed Authority Review locks the tier, evidence sources, exclusions, review rounds, and custom requirements.
No. Connected mode keeps the external CMS or agency-managed site as the live source of truth. Native mode moves the public website to Intakit. Both use the same approval, evidence, and attribution standard; tenant isolation applies to Intakit-controlled data and connector surfaces, while the external CMS remains governed by its owner and hosting provider.
No responsible migration provider can guarantee a search-engine outcome. Intakit’s production launch covenant requires the agreed URL inventory, governed route outcomes, rendered metadata and content comparison, protected-journey and analytics proof, rollback rehearsal, and post-launch monitoring to be green before customer DNS moves.
No. DONNA can draft and assemble evidence, but a human with Site Publisher authority must approve every public revision before activation or connector delivery.
Native is sold with an exit covenant: the firm keeps its domain and approved content, and production activation requires a proven export of content, assets, route and redirect manifests, metadata, and publication history. Export is a launch control, not an after-the-fact promise.
The Authority Review is delivered within two business days after complete access. Focused migrations normally produce a working preview in one to two business days and become launch-ready within five business days after Review approval. Content-rich migrations such as Albaugh normally produce a preview in two to three business days and target launch-ready within ten business days. Custom sites are scoped individually. Customer approvals, missing evidence exports, third-party credentials, and DNS windows pause the clock. Hypercare continues for 30 days after launch.
Often, yes, once complete source access exists. A first automated import and working preview may be produced in one business day. We do not call it launch-ready until route inventory, visual and factual approval, protected-journey and analytics proof, accessibility and performance checks, and rollback are complete. Productized delivery is measured in business days—not months.
The fee reflects the authority under management and the launch responsibility, not hours spent typing. It includes cumulative route discovery, content and metadata migration, asset handling, protected Intakit integration, rendered parity certification, launch coordination, rollback preparation, and 30 days of hypercare. Automation makes delivery faster and more consistent; it does not reduce the value or risk of the outcome.
Native recurring billing begins when the customer-domain site launches. Customer or vendor delay after an accepted preview is handled under the signed migration scope or a written change order; it does not silently start the website subscription early. Migration and recurring Sites access remain separate value units.
Native can remove the recurring hosting, CMS maintenance, plugin, security, backup, and form-integration layer. It does not include unlimited copywriting, photography, campaigns, backlink outreach, or unrelated custom applications.
Often, when it replaces verified spending on hosting, CMS and plugin maintenance, security and backups, form integration, and recurring technical remediation. The Authority Review records what the firm pays today and distinguishes costs that disappear, costs that remain, and capabilities that move into Intakit. We do not compare the full Enterprise operating-platform subscription to website hosting alone; the Native decision is based on verified avoidable spend, operational risk removed, and integration gained.
No. Native Sites runs in a separate public-only service with no Intakit session, client, matter, document, billing, or AI-provider access. Secure intake and portal journeys open the protected Intakit origin by normal HTTPS navigation; the public site does not receive privileged cookies or broad cross-origin API access.
Your public domain stays yours and points to the isolated Sites service only after route, TLS, analytics, and rollback evidence is green. Your protected Intakit app remains a separate origin with its own host-scoped session security. Email and unrelated DNS records are inventoried and left untouched during the website cutover.
Aegis is the professional-service delivery method behind the Authority Review and Authority Migration. It inventories authority, governs the rebuild, certifies the launch evidence, and coordinates cutover and hypercare.