Where do I open a technical support ticket?

Use the CodeCanyon item support channel associated with your purchase. That keeps eligibility, version, and license context attached to your request.

What information should I include in a ticket?

Include your deployment target (Vercel/Fly/etc.), Supabase project region, Node version, reproduction steps, and logs (redact secrets). Faster tickets are specific tickets.

Do you help with HIPAA implementation?

We can help with technical architecture questions, but HIPAA compliance is a shared program across hosting, policies, and operations. Start with the security page and your legal counsel.

Support center

Everything you need to deploy, customize, and scale your CareNova instance in 2026—without guessing which link is “official.”

Documentation

Installation, database setup, and module customization entry points.

Open help center →

Changelog

Track what shipped, what changed, and what to verify after upgrades.

View changelog →

CodeCanyon support

Purchasers should use the item support system for prioritized assistance.

Go to item page →

Product pillars

Understand positioning: clinic OS vs SaaS architecture vs security.

Healthcare SaaS development →

Response time expectations

CodeCanyon item support response times depend on queue volume, but most technical tickets receive an initial reply within one to two business days when reproduction steps are clear. Sales and licensing questions sent by email typically receive a response within 48 hours.

Support — FAQ

Keep exploring CareNova

Jump to the most relevant product pages and a deeper blog article to help you evaluate CareNova faster.

Support center

Documentation

Changelog

CodeCanyon support

Product pillars

Response time expectations

Support — FAQ

Keep exploring CareNova

Related pages

Recommended reading

Support center

Documentation

Changelog

CodeCanyon support

Product pillars

Response time expectations

Support — FAQ

Keep exploring CareNova

Related pages

Recommended reading