AI site operator for small teams
Start with a free OG and metadata check- Build locally with WaastWeb and your coding agent.
- Push source changes into Waastly for review, preview, and safe publishing.
- Use Site Health to keep broken links, metadata, performance, and content drift visible.
Waastly gives technical teams a safer operating loop for their website:
- Local WaastWeb projects you can own and export
- CLI push into a managed review and publish path
- CMS, file library, redirects, and hosting in one control room
- Site Health findings that turn into reviewed fixes
- Rollback-friendly static deployments
Edit locally. Review in Waastly. Publish when the candidate is ready.
Waastly is the operating layer between a real WaastWeb project on disk and the managed site your customers see live.
Update the homepage positioning and make sure it still builds.|
Let me inspect the local WaastWeb checkout, product docs, and current route structure...
README.md→Positioning: AI site operatorsrc/pages/page.tsx→Homepage source loadedwaastly status→No local or server divergenceThe live copy is wider than the current product. I will narrow it to the local-first review workflow.
Here's my plan:
- Refresh hero copy
- Remove stale product claims
- Build locally
- Prepare a review candidate
Hero Section→Local-first site-operator copySite Sections→Claims aligned to review/publishwaastly build→Static build passeswaastly push --dry-run→Review payload checkedReady to queue a review candidate - approve before it can go live.
Review candidate ready
The site change is inspectable in Waastly with build output, changed files, and preview.
The source update stays local until it builds, passes dry-run checks, and becomes a review candidate in Waastly. Nothing reaches live without approval.
Find the highest-risk issues on our website before launch.|
Let me inspect the public pages, metadata, internal links, and asset references...
Generated Routes→12 pages foundSitemap→Only homepage listedOpen Graph Tags→Shared image presentThe sitemap is stale and blocks discoverability. I will propose a source fix first.
Here's my plan:
- Remove stale manual sitemap
- Let WaastWeb generate all routes
- Build candidate
- Review diagnostics
public/sitemap.xml→Manual stale file removedwaastly build→Sitemap regeneratedReview Build→No publish until approvedSitemap fix is ready for review.
Finding resolved in candidate
The generated sitemap now reflects the build output and can be inspected before publish.
Site Health turns a concrete finding into a scoped source change, then routes it through the same review and publish gate.
Ship this only after I inspect the changed files and preview.|
Let me prepare the review summary, candidate build, and rollback context...
Changed Files→8 source changesPreflight→Build readyDeployment History→Rollback target availableThe candidate is ready, but live stays unchanged until a human approves the promotion.
Here's my plan:
- Open review URL
- Inspect source diff
- Check preview
- Approve publish or send back
Review Candidate→Deployment readyPreview URL→Human inspection requiredPromote→Blocked until approvalApprove this deployment to make it live.
Published after approval
The current deployment pointer flips only after the approved candidate is promoted.
Waastly keeps publishing explicit: a green candidate, a review URL, a human approval, and rollback if the new deployment should be reverted.
A control room for the site you already own.
Waastly watches for the issues small teams usually discover too late: broken links, stale metadata, missing assets, risky source changes, and pages drifting away from the business.
Watch
ObserveTracks the pages, metadata, links, and assets that make the site feel cared for.
Triage
PrioritizeGroups findings by risk and impact so the next fix is obvious.
Draft fixes
Review firstTurns approved findings into source changes that you can inspect before anything ships.
Publish safely
Approval gateBuilds a review candidate, waits for approval, and keeps rollback available.
Push a real site change through review.
Join the private alpha for the local WaastWeb workflow: edit on disk, build locally, push to Waastly, review, and publish only when the candidate is ready.
Repeatable website work, made reviewable
Protocols are playbooks for common site improvements. They help scope the work, gather the right assets, and turn the outcome into a reviewable change.
Get notified when SEO Content Cluster is ready.
Get notified when Product Launch Campaign is ready.
Get notified when Email Nurture Sequence is ready.
Get notified when Competitor Comparison Pages is ready.
Get notified when Case Study Template is ready.
Get notified when Referral Program Page is ready.
You're still in the driver's seat.
Agents handle the heavy lifting, but every tool they use is yours too. Edit content directly, manage files, configure SEO. The full platform is built for humans as well.
WaastWeb Source & Hosting
Author real WaastWeb projects locally, then push source changes into managed hosting and review.
CMS Control Room
Manage structured content, preview changes, and keep schema-backed pages out of source-control merge trouble.
Structured Collections
Model repeatable content with typed fields for posts, pages, testimonials, protocols, and other website data.
File Library
Store, organize, and reuse brand assets, images, documents, and generated file references across the site.
Review & Publish
Every source change becomes a review candidate with changed files, build status, preview, and an approval gate.
Site Health
Catch stale metadata, broken links, missing assets, and quality issues before they linger on the live site.
SEO & Analytics
Keep Open Graph, structured data, performance signals, and lightweight analytics context available for reviews.
Multi-locale
Manage content across languages from one place, preview by locale, and publish when each version is ready.
API-first Delivery
Use REST and OpenAPI for integrations while the web app and CLI ride the same public contract.
File Manager
Upload, organize, and reference images and documents through folders, metadata, and managed delivery.
Your website should be a living system, not a launch artifact.
Waastly connects local source, CMS content, files, review builds, publishing, and Site Health around the website your customers actually visit.
Your site is a real TSX project on disk. Pull it, edit it locally, build it, and keep the source portable.
Push source changes into Waastly, inspect the candidate build, and publish only after the review is ready.
Preview changes, track findings, keep audit history, and roll back if a deployment needs to be reverted.
Keep your website improving after launch.
Join the waitlist for the Waastly private alpha. We are looking for technical founders, agencies, and operators who want a safer local-first website workflow.