Homeo AI vs CurenexAI: Free Beta or Review Copilot?

Quick answer

Choose CurenexAI when a qualified homoeopathic practitioner wants to test a browser-based clinic suite that currently combines patient records, repertory search, AI suggestions, consultation history, digital prescriptions, follow-ups, lab context, and image-assisted analysis in one free beta. Choose Homeo AI when the main need is a review copilot that keeps the consultation narrative visible, proposes an editable case structure, supports review of rubric mappings and source passages, and preserves practitioner-owned reasoning into follow-ups.

The free label is useful for evaluation, but it is not a lifetime price promise. CurenexAI's official terms and privacy policy, both marked as updated on 27 July 2026, say paid plans or feature tiers may be introduced. The terms promise existing users at least 30 days notice before pricing changes. A clinic should therefore test both present capability and the cost, export, and continuity questions that would matter after the beta.

What changed on 27 July 2026

The current official CurenexAI homepage describes a broad product: patient management, AI-powered remedy suggestions using Gemini, a local RAG-based disease-diagnosis feature, image-assisted Dermo analysis, a digital repertory, prescriptions, follow-up tracking, and lab-report analysis. It also labels the product a free beta for homoeopathic doctors. These are vendor descriptions of the current platform, not independent proof of accuracy, clinical benefit, legal compliance, or uninterrupted availability.

The newly dated privacy policy makes the product boundary more concrete. It says the service collects practitioner credentials and may hold patient demographics, contact details, medical history, symptoms, consultation records, prescriptions, lab reports, and skin images. It distinguishes local processing for the disease-diagnosis feature from Gemini processing for remedy suggestions and Dermo. For Gemini requests, the vendor says relevant consultation data or images are sent without patient-identifying information and are not stored by Google.

Those statements are important procurement evidence, but they still require a clinic to verify the implemented data flow. Ask which fields are removed, how free text is scrubbed, which Gemini service and contract apply, where requests are processed, what logs remain, who can access support records, and how a clinic can prove deletion. A marketing or policy statement is not a substitute for a data-flow diagram, signed terms, and a test of the exact account configuration.

CurenexAI's genuine strength is breadth

CurenexAI is designed as an end-to-end operating surface. A practitioner can create a patient record, save consultations, search a repertory, review AI suggestions, prepare a prescription document, track follow-ups, and keep related material together. For a clinic currently moving between paper notes, a separate repertory, a word processor, and a patient list, that breadth may remove handoffs.

The official FAQ also describes practical controls. Each doctor is said to see only patients they created. New-device login ends prior sessions. Account deletion is available through support. Prescription and consultation records can be printed. The AI suggestion feature is described as reference-only, and the FAQ tells practitioners to cross-check repertory and materia medica before deciding.

The beta can therefore be a useful way to test a whole clinic workflow without first committing to a subscription. It also exposes more operational questions than a narrow analysis tool. A platform that stores identities, contact details, images, prescriptions, consultations, and lab reports has a larger data and continuity surface. Breadth is valuable only if every part of that surface passes the clinic's consent, access, correction, retention, backup, and export review.

Free beta does not remove switching cost

The official FAQ says bulk export is still being developed. It currently directs users to print records or contact support for export assistance. The privacy policy says patient records remain until deletion or account closure, activity logs are retained for 90 days, and backup data may remain for up to 30 days after deletion. The terms advise keeping backup records and say the service is not guaranteed to be uninterrupted or error-free.

That combination should shape the trial. Do not wait until a full patient history is inside the system to learn what an export contains. Before adoption, request a sample export for patients, consultations, prescriptions, uploaded files, repertory decisions, audit history, and follow-up links. Check whether the export is structured, readable without the service, complete across dates, and practical to import elsewhere. Record how long a support-assisted export takes.

Future pricing should be tested in the same way. Ask what remains available if a clinic declines a future paid plan, whether read-only access continues, how long export remains open, which features might be placed in separate tiers, and whether early-beta data can be removed before billing begins. The vendor promises notice, but the clinic still needs a documented exit path.

Where Homeo AI fits differently

Homeo AI is the stronger fit when the bottleneck is reviewable reasoning rather than running every clinic operation in one product. Its evaluation should begin with fidelity to the original case narrative: whether location, sensation, modalities, chronology, intensity, mental and physical qualifiers, and the practitioner's corrections remain visible.

The useful output is not merely a ranked remedy list or a finished prescription. It is a traceable working path from original wording to a proposed structure, candidate rubric mappings, inspected source material, a practitioner-edited differential, and the logic carried into follow-up. A clinic that already has scheduling, billing, records, and prescribing systems may prefer a focused reasoning layer rather than replacing the surrounding stack.

Homeo AI does not escape procurement review because it has a narrower job. Confirm its current access controls, processing, retention, deletion, exports, support access, logs, and incident process before using identifiable information. A reviewable interface reduces clinical opacity; it does not by itself establish privacy, security, or legal suitability.

A reproducible clinic test

Prepare twelve completed, de-identified cases with different narrative styles and follow-up patterns. Remove names, contact details, dates of birth, record numbers, exact visit dates, faces, images, addresses, and rare combinations that could identify a person. Keep a separate answer packet with the original narrative, accepted symptom structure, rubrics reviewed, source passages checked, final practitioner reasoning, and known follow-up changes.

Run six workflow tests in each product:

1. Enter the same de-identified consultation text and record how much original wording survives. 2. Mark every proposed symptom structure or rubric that a practitioner must correct. 3. Time how long it takes to inspect the evidence behind a material suggestion. 4. Reopen the case as a follow-up and check whether earlier reasoning remains reconstructable. 5. Export or print the complete record and compare it with the on-screen version. 6. Delete a test record and document the visible, support, log, and backup behavior promised by the applicable policy.

For CurenexAI, also test the clinic-suite seams: patient creation, consultation linkage, repertory search, prescription document, follow-up, role isolation, session behavior, and support-assisted bulk export. Do not upload a real skin image or lab report. Use synthetic files specifically created for the test. Record which feature uses local RAG processing and which invokes Gemini according to the product interface and current policy.

For Homeo AI, score narrative fidelity, mapping transparency, source traceability, correction time, differential clarity, and follow-up continuity. Do not penalize it for lacking a billing or prescription module if those jobs already belong to another system. Likewise, do not judge CurenexAI only as a note-analysis tool when its main advantage is the connected clinic workflow.

Have a second qualified practitioner review the results without knowing which product produced each export. Use separate scores for clinical-review burden, record completeness, operational breadth, data portability, and support dependency. A long feature list should not outweigh a material error, and a polished summary should not outweigh lost patient wording.

Safety and known limits

CurenexAI's own terms describe its AI outputs and diagnosis feature as decision support that must be independently verified. Homeo AI must be used with the same discipline. A local database, Gemini request, repertory result, proposed rubric, ranked remedy, cited passage, or generated document can be incomplete or wrong.

Use only completed, de-identified cases until the clinic has approved the entire data flow and legal basis. Neither product replaces diagnosis, referral, emergency care, practitioner judgment, prescription, potency, dosage, or follow-up responsibility. Neither should make an emergency-care decision or decide whether a person needs urgent conventional assessment. If a case presents urgent or worsening risk, use the appropriate medical and emergency pathway.

Do not infer independent certification from a vendor compliance label. Verify the legal entity, jurisdiction, contracts, subprocessors, hosting, incident response, access logs, backup design, deletion process, and exact account features. The practitioner remains responsible for consent, record accuracy, clinical review, and safe handoff.

Conditional verdict

Choose CurenexAI when the clinic wants to trial an integrated homoeopathic workspace and is prepared to test the beta's data flow, future pricing, support-assisted export, backups, and operational continuity before adding identifiable records. Its genuine strength is the breadth of the current clinic workflow.

Choose Homeo AI when the clinic already has its operational systems and needs a focused, correctable path from consultation language through rubric and source review to practitioner-owned follow-up reasoning.

Use both only if ownership is explicit. Decide which system is authoritative for identities, records, prescriptions, analysis, and follow-ups; minimize copied data; test export from both; and document the handoff. A free beta is a chance to measure fit, not a reason to skip governance.

Official sources checked

• CurenexAI official product page
• CurenexAI official FAQ and beta pricing
• CurenexAI privacy policy updated 27 July 2026
• CurenexAI terms updated 27 July 2026

Product facts reviewed 2026-07-27. Confirm current features, prices, source libraries, and terms with the vendor.