Onboarding

When approved, PolySwarm will require a Know Your Customer (KYC) check so we understand who owns and operates the Engine.

You will be asked to submit:

You will also receive an Engine Provider Agreement for signature. We must have a signed agreement in place before we can proceed to provisioning.

Onboarding checklist

If you have chosen to deploy your Engine through PolySwarm, and allow us to host it we will need additional technical information:

Is the Engine containerized, what is the image size, and how can we access the image?
What is the update mechanism, and how often does it update?
Does it require internet access?
What resources are required (memory, CPU, disk)?
If it is Windows-based, can it run under Wine?

If you choose to host the Engine yourself, then the process is:

PolySwarm creates the Engine in a development state until verification is complete
You create engine webhooks in your team account, connect an engine webhook to the Engine to begin testing.
Test in the Development Community: Send test bounties to confirm the Engine processes artifacts and responds correctly
Request verification: When ready, request verification from the My Engines tab in your Team.

During verification testing, common issues include:

Slow or inconsistent responses
Incorrect verdict formatting or missing required fields
Accuracy problems across benign and malicious samples
Unexpected errors during bounty processing
If verification fails, fix the issues, re-test in the Development Community, then request verification again.