Business Email
Use email for pre-sales consultation, enterprise cooperation, membership planning, and manual order coordination.
service@relation-graph.com
Current status
Free Access
Available
MIT-licensed core, public docs, and self-service project validation.
Support desk
Customer Service
Use this page for contact channels, issue preparation guidance, and a public explanation of how support levels differ.
Contact channels
Who to contact and when
Choose the channel based on whether the issue is private and transactional, or public and product-oriented.
Service Email
Use email for invoice requests, payment questions, order follow-up, and materials that need to be archived.
service@relation-graph.com
GitHub
Use the public repository for product feedback, documentation suggestions, and community-visible questions.
Open repositoryBefore you contact us
What helps us respond faster
A short but concrete issue summary is usually more valuable than a long message without reproducible details.
For implementation or delivery coordination
When you need human support, project context matters more than the final question alone.
- Explain whether you are evaluating, building a demo, or already delivering a real project.
- State the expected timeline or delivery pressure.
- List the specific blocker, expected output, and current workaround if any.
Support levels
How support is structured
The support model is intentionally layered: public channels cover general questions, paid plans reduce delivery friction, and enterprise service adds stronger coordination for real project execution.
Free
The open-source core, public docs, and GitHub remain the baseline support path for general product questions.
- Best fit for self-driven evaluation and early-stage integration.
- Use GitHub and public documentation first for broadly applicable questions.
- A good default when direct coordination is not yet necessary.
Pro
Pro is designed to reduce repeated exploration by providing stronger implementation references and a faster path for smaller delivery tasks.
- Best fit for individual developers, consultants, and smaller project delivery.
- Useful when examples and implementation references matter more than formal coordination.
- Often the pragmatic middle step between self-service and enterprise delivery.
Enterprise
Enterprise is for teams, customer projects, and procurement flows that need clearer communication, faster response, and better delivery coordination.
- Best fit for team projects and enterprise procurement scenarios.
- Stronger for invoice, order, and support process standardization.
- A better choice when delivery risk is more important than minimizing spend.