Core Care

The description states that Core Care is a bilingual desktop health application for Windows and Linux, designed to bring together multiple system maintenance functions into one interface. It includes:

• Smart Cleaner with risk-level classification (Safe, Review, Protected)
• Disk Health
• Startup analysis
• Updates guidance
• Driver Recovery
• Privacy tools
• Performance recommendations
• Health Overview combining findings from all sections

It is described as a local-first tool, meaning scan inventories and findings remain on the user's computer. The application uses a safety model that involves detection, explanation, approval, revalidation, and recovery before any action.

The product is built using:

• C#, .NET 9
• Avalonia UI
• Codex for development assistance
• GitHub Actions and Velopack for CI/CD

Not evidenced: No revenue, customer data, or actual user adoption.

The author positions Core Care as a safer alternative to existing cleanup tools, which they claim have broken systems in the past. The tagline — “Clean your computer without breaking it” — reflects this positioning.

Key claims:

• Explains every risk
• Protects important files
• Keeps maintenance decisions in the user's hands

The evolution of the product appears to be from an idea (inspired by failed cleanup tools) to a working beta with cross-platform support, iterative development using Codex, and integration of safety workflows.

Inference: The positioning implies a niche in system maintenance where trust and transparency are key differentiators — but no evidence of market validation or competitive differentiation beyond self-reporting.

The description states that Core Care is aimed at users who want to maintain their computers safely, especially those who may not be technically inclined but still need to manage system health.

It targets:

• End-users seeking safe cleanup and maintenance
• People who have experienced issues with other tools
• Users who value control over automated actions

Not evidenced: No specific customer segments, personas, or user research data. The ICP is inferred from the product’s intended use case and safety-focused approach.

The description states that Core Care is currently a free beta. There is no mention of monetization plans, pricing tiers, or commercial models beyond the current free access.

Inference: If this remains a free tool, it may be positioned as either:

• A utility with potential for freemium upsells
• A developer-side tool for personal use only

Not evidenced: No revenue model, pricing strategy, or monetization path described.

The application is built using:

• C#, .NET 9
• Avalonia UI
• Codex for development
• GitHub Actions and Velopack for release pipelines

It supports:

• Windows and Linux platforms
• Cross-platform architecture with shared safety engine and platform-specific integrations
• Local-first processing (no upload of scan data)
• Protected-path and cleanup-classification tests
• Automated testing, dependency audits, and release builds

Not evidenced: No information on scalability, performance metrics, or production deployment details.

The project is described as a beta with:

• Working Windows and Linux desktop releases
• Czech and English interfaces
• Installable releases with in-app update support
• Automated tests and release pipelines

It was submitted to the OpenAI 2026 hackathon, suggesting it is a developer-side prototype or early-stage product, not yet commercially launched.

Not evidenced: No user base, downloads, usage statistics, or adoption data. The project has no demonstrated traction beyond its own development cycle.

The author does not reference specific competitors. However, the product’s positioning suggests it competes with:

• General-purpose system cleaners
• Maintenance tools for Windows and Linux
• Tools that automate cleanup without user control

Not evidenced: No competitive analysis, market sizing, or differentiation from existing solutions.

• No verified users or traction: The product is described as a beta with no evidence of real-world usage.
• Single developer team: Only one member listed (Jan Kaczmarczyk), raising questions about scalability and long-term maintenance.
• Self-reported claims only: All descriptions are unverified, including the effectiveness of safety mechanisms.
• No monetization strategy: The tool is free, with no indication of how it will become sustainable or generate revenue.
• Limited platform support: While cross-platform, it’s currently in beta and lacks macOS support.

1. What specific problems have users encountered during the beta phase?
2. How does Core Care handle edge cases where file ownership is ambiguous?
3. Are there any plans to monetize the tool beyond its current free beta?
4. What are the technical limitations of the current implementation that might prevent scaling?
5. Has the team considered how to onboard non-technical users effectively?
6. How do you plan to ensure long-term maintenance and updates for both Windows and Linux?