[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-11119":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":15,"stars7d":17,"stars30d":18,"stars90d":16,"forks30d":16,"starsTrendScore":17,"compositeScore":19,"rankGlobal":10,"rankLanguage":10,"license":20,"archived":21,"fork":21,"defaultBranch":22,"hasWiki":21,"hasPages":21,"topics":23,"createdAt":10,"pushedAt":10,"updatedAt":24,"readmeContent":25,"aiSummary":26,"trendingCount":16,"starSnapshotCount":16,"syncStatus":27,"lastSyncTime":28,"discoverSource":29},11119,"Anybackup","anybackup-ai\u002FAnybackup","anybackup-ai","An AI-Native Data Resilience Platform — autonomous backup, recovery, and optimization. Built on an open-source model, delivering 35% lower TCO than traditional approaches.","",null,"Python",262,54,16,1,0,3,119,58.72,"Other",false,"main",[],"2026-06-12 04:00:53","# Anybackup\n\n\u003Cp align=\"center\">\n  \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fanybackup-ai\u002FAnybackup\u002Fblob\u002Fmain\u002FLICENSE\">\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Flicense-SSPL--1.0-blue.svg\" alt=\"License\">\u003C\u002Fa>\n  \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fanybackup-ai\u002FAnybackup\u002Fblob\u002Fmain\u002FVERSION.txt\">\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fversion-9.0.0--alpha-orange.svg\" alt=\"Version\">\u003C\u002Fa>\n  \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fstatus-alpha_preview-yellow.svg\" alt=\"Status\">\n  \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Farchitecture-AI--Native-brightgreen.svg\" alt=\"Architecture\">\n  \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fworkload-MySQL_first-informational.svg\" alt=\"Workload\">\n  \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fcloud--native-Kubernetes-326CE5.svg\" alt=\"Cloud Native\">\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  \u003Cstrong>AI-Native Data Resilience Platform\u003C\u002Fstrong>\u003Cbr>\n  Backup, recovery, and operational assurance through explainable agent workflows.\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  \u003Ca href=\".\u002FREADME_zh.md\">中文\u003C\u002Fa>\n\u003C\u002Fp>\n\n---\n\n## Product Positioning\n\nAnybackup V9 is a more economical and intelligent data resilience platform. Built on an open-source business model, it helps customers achieve the data resilience their business requires. Powered by Anybackup Agent as an AI backup administrator, the platform enables autonomous backup, autonomous recovery, and autonomous optimization, reducing total cost of ownership by up to 35% and moving teams beyond reactive response.\n\n---\n\n## Why Anybackup Exists\n\nTraditional backup systems are usually powerful after you already know what to click, which policy to configure, which recovery point to choose, and which risk you are about to create. That is exactly the problem.\n\nAnybackup V9 is not trying to put a chatbot on top of backup software. It is rebuilding the backup and recovery experience around an AI-native workflow:\n\n1. Describe the data protection need in natural language.\n2. Let the Agent generate a structured plan with assumptions and risks.\n3. Keep the human in control for dangerous actions.\n4. Let Foundation execute the confirmed backup or recovery task.\n5. Keep the decision and execution trail auditable.\n\nThe goal is simple: make data resilience easier to operate without making it vague, magical, or unsafe.\n\n---\n\n## What This Repository Represents\n\nThis is the open-source repository for **Anybackup V9**, the full platform direction:\n\n| Product part | What it does |\n|---|---|\n| **Anybackup Agent** | Understands intent, generates backup and recovery plans, explains risk, manages confirmation, and keeps decision context |\n| **Anybackup Foundation** | Executes backup, recovery, retention, and data protection operations |\n| **Anybackup Client** | Connects protected workloads and provides workload-side data access |\n\nAnybackup Agent is cloud-native and must be deployed on Kubernetes. Anybackup Foundation is host-deployed and runs on managed infrastructure outside the Agent Kubernetes runtime. This README keeps deployment details compact, but it should still respect the real product structure.\n\n---\n\n## Product Capabilities\n\n### Natural-Language Backup Planning\n\nDescribe a workload and Anybackup Agent turns the request into comparable backup plan candidates. The plan is not just a sentence: it should explain frequency, recovery point expectations, risk trade-offs, and why one option is recommended.\n\n### Recovery Plan Generation\n\nDescribe a MySQL failure and the Agent turns it into a structured recovery plan. The plan identifies recovery scope, target point, execution path, and the risk of overwriting or rolling back data.\n\n### Human-Controlled Execution\n\nAny action that can damage production data must go through explicit human confirmation. Anybackup treats AI as a planning and decision-support layer, not as an unchecked operator.\n\n### Operational Query\n\nAdministrators can ask about backup jobs, recovery progress, and platform state in natural language instead of hunting through raw system details first.\n\n### Audit-Friendly Workflow\n\nThe conversation, generated plan, human decision, execution request, and result should remain traceable. This is essential for real backup and recovery operations, where \"why did this happen\" matters as much as \"did it run.\"\n\n---\n\n## Current Alpha Scope\n\n`9.0.0-alpha` is an early public preview. It is focused, deliberately narrow, and meant to prove the core loop before the platform grows wider.\n\n**In scope now**\n\n- Single backup administrator workflow\n- MySQL-first backup and recovery scenarios\n- Backup recommendation from natural language\n- Recovery plan generation from failure descriptions\n- Human confirmation before risky execution\n- Foundation-backed execution path\n- Basic operational query experience\n\n**Not promised by this alpha**\n\n- Complete multi-tenant SaaS operations\n- Full enterprise role and permission model\n- Broad workload coverage beyond the first MySQL scenarios\n- Fully automated multi-step recovery without operator review\n- A polished production installer for every environment\n\nThis boundary is intentional. A reliable AI-native data resilience platform should earn trust one operational loop at a time.\n\n---\n\n## Deployment Overview\n\nAnybackup V9 is installed through the integrated deployment entrypoint. Before running the installer, prepare the model configuration from the provided template, then run [deploy\u002Finstall.sh](.\u002Fdeploy\u002Finstall.sh) and follow the installer prompts for required credentials.\n\nLocal single-node installation example:\n\n```bash\ncd deploy\n.\u002Finstall.sh \\\n  --local \\\n  --foundation-mode integrated \\\n  --foundation-self-ip \u003Cfoundation-private-ip>\n```\n\nThe installer prepares the Kubernetes runtime, deploys KWeaver, Foundation, FoundationClient, Anybackup Agent content, and business services, then publishes the Web access entrypoint.\n\nFor detailed deployment steps, model configuration, and credential input methods, see [deploy\u002FDEPLOYMENT_en.md](.\u002Fdeploy\u002FDEPLOYMENT_en.md).\n\n---\n\n## Example Workflows\n\n### Backup Recommendation\n\n```text\nUser:\nRecommend a backup plan for our production MySQL database.\n\nAnybackup Agent:\nI found three candidate plans:\n\n1. Standard protection\n   Weekly full backup + daily incremental backup.\n\n2. Low-RPO protection\n   Weekly full backup + daily incremental backup + minute-level log backup.\n\n3. Simple protection\n   Daily full backup.\n\nRecommended: Low-RPO protection, because this database is production-facing\nand needs a shorter recovery point objective.\n```\n\n### Recovery Plan\n\n```text\nUser:\nThe production MySQL instance crashed and all databases are unavailable.\n\nAnybackup Agent:\nThis looks like an instance-level failure.\n\nRecommended recovery:\n- Scope: full MySQL instance\n- Target: latest valid backup point\n- Execution: restore through Anybackup Foundation\n- Risk: this may overwrite current data on the target host\n\nPlease confirm before execution.\n```\n\n---\n\n## Architecture at a Glance\n\n```text\nNatural language request\n        |\n        v\nAnybackup Agent\nIntent, plan, risk, confirmation, audit context\n        |\n        v\nAnybackup Foundation\nBackup, recovery, retention, execution\n        |\n        v\nAnybackup Client\nProtected workload access and data collection\n```\n\nThe platform design separates **decision**, **execution**, and **workload access**. That separation matters: AI can help decide and explain, Foundation executes confirmed operations, and Client-side capabilities connect the protected environment.\n\n---\n\n## Repository Map\n\n```text\nAnybackup\u002F\n├── Agent\u002F          # AI interaction and decision layer\n├── CLI\u002F            # Internal command-line tooling and control utilities\n├── deploy\u002F         # Cloud-native deployment assets\n├── LICENSE         # SSPL-1.0\n├── NOTICE          # Copyright notice\n├── README.md       # English README\n├── README_zh.md    # Chinese README\n└── VERSION.txt     # Current version\n```\n\nCLI and deployment assets exist because real platforms need engineering tools. They are not the main story of this README. The main story is the product capability: AI-native backup, recovery, and data resilience.\n\n---\n\n## Open Source Model\n\nAnybackup is released under [SSPL-1.0](.\u002FLICENSE). The project uses an open-source model to make the platform direction visible, inspectable, and extensible while preserving a sustainable path for enterprise-grade development.\n\nThird-party notices are maintained alongside distribution units where applicable. See [NOTICE](.\u002FNOTICE) and component-level `THIRD_PARTY_NOTICES.md` files for details.\n\n---\n\n## Community\n\n- Issues: [GitHub Issues](https:\u002F\u002Fgithub.com\u002Fanybackup-ai\u002FAnybackup\u002Fissues)\n- Discussions: [GitHub Discussions](https:\u002F\u002Fgithub.com\u002Fanybackup-ai\u002FAnybackup\u002Fdiscussions)\n\n---\n\n## Contributing\n\nContributions are welcome as the project evolves. Before submitting a pull request:\n\n1. Open an issue to discuss the change or feature.\n2. Keep changes aligned with the current alpha scope.\n3. Update relevant documentation and notices when behavior or dependencies change.\n4. Run checks for the component you modified.\n\nDetailed contribution guidelines will be expanded as the public development workflow matures.\n","Anybackup是一个基于AI的原生数据韧性平台，旨在实现自主备份、恢复和优化。该项目采用Python语言开发，通过可解释的代理工作流提供数据保护服务，相比传统方法能降低35%的整体拥有成本。其核心功能包括通过自然语言描述数据保护需求、由代理生成结构化计划并评估风险、执行确认后的备份或恢复任务，并保持决策和执行轨迹的可审计性。Anybackup适用于需要高效且智能的数据管理解决方案的企业级场景，特别是在云原生环境中运行MySQL等数据库负载时更为适用。",2,"2026-06-11 03:31:12","CREATED_QUERY"]