Lyna
SupportBlog
IntroductionFeaturesIntegrationsTips & TricksChangelog

Support

How to get help, what support covers, and where to find community resources.


Support channels

Community Discord

Open to everyone. The primary community hub.

  • Ask questions and get help from the community and Lyna team
  • Share projects and get feedback
  • Report bugs and suggest features
  • Follow announcements and changelog updates

Fastest way to get answers for general questions.

Email support

For account issues, billing, or anything that needs a private channel: support@lyna-it.com.

PlanResponse time
FreeCommunity support only (Discord)
ProWithin 48 hours
TeamWithin 24 hours
EnterpriseWithin 4 hours (business days)

Dedicated account manager (Enterprise)

Enterprise subscribers get a dedicated account manager for onboarding, technical guidance, custom integrations, and escalations.


What support covers

Included

  • Platform issues: Editor, canvas, AI chat, code editor, publishing
  • Account and billing: Plan changes, payments, subscriptions
  • Integration help: Connecting Supabase, Stripe, GitHub, Figma, MCP servers
  • Getting started: Feature guidance and best practices
  • Bug reports: Unexpected behavior, errors, crashes
  • Feature requests: Suggestions for improvements

Not included

  • Custom app development: We cannot build your app or debug custom business logic
  • Third-party service issues: Problems with Supabase, Stripe, or GitHub should go to those providers
  • Design direction: Aesthetic choices and design strategy
  • Code review: Application code quality, security, or performance review (though the AI can help)
  • Uptime SLA for Free plans: No SLA guarantee on Free

Tip

Try the AI chat's Ask mode first. It can explain your code, suggest approaches, and diagnose issues in context. Often faster than waiting for a support response.


How to report a bug

Include as much of the following as you can:

  1. What you were trying to do: The action or workflow that triggered the issue.
  2. What happened: The actual behavior.
  3. What you expected: What should have happened.
  4. Steps to reproduce: Numbered steps someone can follow.
  5. Screenshots or recordings: Visual evidence helps a lot.
  6. Error messages: Full text from the chat panel, browser console, or code editor.
  7. Browser and OS: Which browser and operating system.

Report through Discord (bug reports channel) or email support@lyna-it.com.


Community resources


Support FAQ


Contact summary

ChannelWho can use itBest for
DiscordEveryoneGeneral questions, community help, bug reports, feature requests
Email (support@lyna-it.com)Everyone (priority for paid plans)Account issues, billing, private matters
Email (security@lyna-it.com)EveryoneSecurity vulnerability reports
Dedicated account managerEnterpriseAll support needs, onboarding, custom integrations