Site Management & Extensibility

Enterprise-grade tools for managing WordPress site evolution safely and collaboratively. Track changes, control deployments, and coordinate with teams without losing the agility that makes Kintsu.ai powerful.

---

​

Version Control for Site Changes

Track what changed and when, so you can restore a previous version if an edit doesn’t land the way you expected. Version control features:

• Complete change history — Every edit is tracked with timestamps and descriptions
• Detailed diff views — See exactly what changed in each edit
• Change metadata — Who made the change, when, and why
• Branch support — Work on multiple change sets simultaneously
• Commit-like workflow — Familiar version control concepts for WordPress
• Search and filter — Find specific changes quickly
• Export history — Download change logs for external records

Unlike traditional backups that restore everything or nothing, version control gives you surgical precision: see exactly what changed and when.

---

​

Rollback and Undo

Revert individual changes (not just “restore everything”) so you can iterate safely without losing other progress. Rollback capabilities:

• Selective undo — Revert specific changes while keeping others
• Granular rollback — Undo changes to individual sections or pages
• Preserve subsequent work — Roll back without losing later changes
• Rollback preview — See what will change before reverting
• Bulk operations — Revert multiple related changes at once
• Time-based rollback — Restore to a specific point in time

Traditional WordPress backup-and-restore is all-or-nothing. Kintsu.ai’s rollback lets you undo the change that didn’t work while keeping everything else intact.

​

Example Workflow

1. Make five changes to your homepage
2. Discover change #3 caused an issue
3. Roll back only change #3
4. Changes #1, #2, #4, and #5 remain intact

This surgical approach to rollback eliminates the fear of experimenting and iterating on your site.

---

​

Staging-Friendly Workflows

Make and validate changes on staging before pushing them to production — ideal for business-critical sites where mistakes cost money. Staging features include:

• Staging environment sync — Keep staging aligned with production
• Change promotion — Push validated changes from staging to production
• Selective deployment — Promote specific changes, not everything
• Testing validation — Ensure changes work before going live
• Client approval — Let stakeholders review on staging
• Scheduled deployment — Push changes at optimal times

Kintsu.ai treats staging as a first-class concept, not an afterthought. Changes flow smoothly from development to staging to production with full visibility.

---

​

Collaboration and Approvals (Beta)

Let stakeholders review proposed changes (marketing, product, agency, founder) and approve before anything goes live. Collaboration features include:

• Review workflows — Route changes to appropriate reviewers
• Approval gates — Require sign-off before publishing
• Comment threads — Discuss changes with context
• Role-based permissions — Control who can propose vs. publish changes
• Notification system — Alert reviewers when input is needed
• Change annotations — Add notes and context to proposed edits

This is essential for agencies managing client sites or teams where multiple stakeholders need visibility into changes.

​

Use Cases

• Agency workflows — Get client approval before publishing changes
• Marketing teams — Review content changes before they go live
• Enterprise sites — Ensure compliance and brand consistency
• Multi-site management — Coordinate changes across multiple properties

---

​

Audit Trail

A clear record of changes: what was edited, where, and why — so maintenance doesn’t become guesswork later. Audit trail captures:

• Change descriptions — Natural language summaries of what changed
• User attribution — Who made each change
• Timestamps — Precise timing of all modifications
• Affected areas — Which pages, sections, or components were edited
• Reasoning — Why the change was made (if documented)
• Related changes — See connections between related edits
• External integrations — Track changes made via API or CI/CD

Audit trails are invaluable for:

• Compliance — Demonstrate change control for regulated industries
• Troubleshooting — Identify what changed before an issue appeared
• Team handoffs — New team members can understand site history
• Client reporting — Show clients what work was completed
• Long-term maintenance — Document the evolution of the site

---

​

Multi-Site Management

For agencies and teams managing multiple WordPress sites, Kintsu.ai provides centralized visibility and control. Multi-site features:

• Unified dashboard — See all your sites in one place
• Cross-site patterns — Identify common changes across sites
• Shared components — Reuse successful changes across properties
• Bulk operations — Apply similar changes to multiple sites
• Aggregate reporting — Understand activity across your portfolio
• Client segmentation — Organize sites by client or project

Manage five sites or five hundred with the same level of control and visibility.

---

​

Best Practices

​

Document Your Changes

Add context when making changes: why you’re making the edit, what problem it solves, and what outcome you expect. Your future self (and your team) will thank you.

​

Use Staging for Important Changes

Production changes should be routine and low-risk. Save experiments and significant updates for staging environments.

​

Review Audit Trails Regularly

Periodic review of the audit trail helps identify patterns, recurring issues, and opportunities for process improvement.

​

Set Up Approval Workflows Early

Don’t wait until after a mistake to implement review processes. Set up appropriate approval gates from the beginning.

---

​

Pricing

Site management features are included in Professional and Enterprise plans. Collaboration and multi-site features require an Enterprise plan. See our plans and pricing page for details.