The questions that come up most often during the private beta. If yours is not here, email support@malveon.com.
Is Malveon generally available?
Not yet. Malveon is in private beta. The connection, decision capture, health, and deploy-safety surfaces described in these docs are real and in use, and a few areas are still filling in. Where something is partial, the relevant doc page says so plainly.
Do we have to migrate from Jira, Linear, or Slack?
No. Malveon reads from your tools over OAuth and leaves them exactly as they are. Your team keeps using every tool as before. There is nothing to migrate and no agent to install. Setup takes about fifteen minutes.
What does Malveon read, and what does it not?
Malveon reads metadata: pull request titles and statuses, task and issue state, deploy and incident events, and messages in the channels you select. It does not read or transmit your source code. The Deploy Safety scanner runs locally in your editor; only file paths and environment-variable names leave the extension. See Data handling under Security & Privacy.
Will it work if I only connect one tool?
Yes, with the honest caveat that Malveon gets more useful as you connect more. With just a tracker, Malvedeck computes a real health score from task signals at a lower confidence band. Add a CI provider and incident source, and the score blends those in. The fastest first value comes from connecting Slack and GitHub together.
Which tools are supported?
Slack, GitHub, Jira, and Linear are the most complete: connect over OAuth, signed webhook ingestion, and write-back. Datadog, PagerDuty, Sentry, and Vercel connect as signal sources for incidents and CI. Notion, Confluence, Google Docs, and Microsoft Teams connect over OAuth with the beta caveats noted on each integration page.
How is Malveon different from PagerDuty, incident.io, or Linear?
PagerDuty alerts you. incident.io manages the incident. Linear tracks tasks. None of them connect the Slack decision that caused the problem, the PR that shipped it, and the ticket that tracked it into one place. Malveon is the connective tissue between your existing tools, not a replacement for any of them.
How is my data secured?
Connections are OAuth grants you authorize and can revoke. Stored tokens are encrypted at rest. Webhooks from Slack, GitHub, Jira, and Linear are verified with HMAC signatures. Every query is scoped to your company. The full picture, including which connections do not yet sign webhooks, is on the Security & Privacy pages.
Are you SOC 2 certified?
No, and we will not claim it until a third-party audit signs it off. Formal certifications are a roadmap priority. See the Security roadmap page for what is in place today versus planned.
What does it cost?
During the pilot, Malveon is $99 per month flat, with no per-seat pricing and no credit card required to join. Post-pilot pricing is planned per contributor per month. Current pricing is on the malveon.com pricing page.
How do I get help?
Email support@malveon.com, or book a 30-minute setup call with the founding team from the Getting Started page.