Set up your first device

Four short steps. Most teams finish in under two minutes. You can edit any choice later from the device page.

Pick device

Connect

Choose keys

Review

What are you enrolling today?

Pick the device that best matches your hardware. We'll tailor the SDK and key policy.

Connect to PULSE

Sample credentials are pre-filled so you can run the flow end-to-end. Replace with your real key when you're ready to ship.

API key

Looks like qsk_ followed by 32 characters.

Endpoint URL

Use HTTPS. You can change this before deployment.

Region Optional

Set your key policy

Defaults work for most teams. Tune if your threat model needs higher margin or faster rotation.

Algorithm

ML-KEM-512 NIST Level 1 · 128-bit equivalent. Smallest keys, fastest. public 800 B · ciphertext 768 B ML-KEM-768 Recommended NIST Level 3 · 192-bit equivalent. Balanced for IoT. public 1184 B · ciphertext 1088 B ML-KEM-1024 NIST Level 5 · 256-bit equivalent. Maximum margin. public 1568 B · ciphertext 1568 B

Key rotation

Every 7 days High-rotation policy for compliance-sensitive work. Every 30 days Recommended The default most teams pick. Every 90 days Lower operational overhead for constrained devices.

Ready to deploy

Your device will pull key material on first connect. You can edit any field later from the device page.

I understand this device will enroll in the PULSE fleet. Read the device agreement.