Skip to content
    Onboarding

    What Happens After You Sign Up: Your First 24 Hours

    What SeqOps needs access to, why, and how long it takes for your first results to appear.

    SeqOps starts the first scan of a cloud environment within about 15 minutes of connecting it. After that, cloud scans follow your plan's schedule: every two weeks on Core, weekly on Edge and daily on Max. Until something is connected, your dashboard stays empty — that is expected.

    What SeqOps Needs Access To

    SeqOps needs one or both of the following, depending on what you want to monitor:

    Why SeqOps Needs It

    SeqOps collects security metadata: configurations, software versions, security settings and scan results. Cloud access is read-only, and server agents connect outbound only, with no inbound firewall rules and no cloud credentials stored on the server. For where the data is stored, see Where Your Data Lives: Residency & Storage.

    What to Expect in the First 24 Hours

    • •Right after connecting — The cloud environment appears under Cloud → Activation, switched on, with a Next Scan On date. A server appears once its agent registers.
    • •Within about 15 minutes — The first cloud scan starts, and resource inventory, findings and configuration results begin to populate.
    • •After the first results — Review your dashboard, set up notifications, and invite your team. See the Onboarding Checklist for Security Teams.

    If Nothing Appears After 24 Hours

    Check that each cloud environment is switched on under Cloud → Activation and that each server appears in Server List. If data still hasn't appeared, contact support@seqops.io or use the Contact Us page with the provider or server name and any error you received.

    onboardingfirst stepstimingaccessmetadata

    We use cookies

    We use essential cookies to run this site. With your permission, we'd also like to use analytics cookies to see how the site is used, and functional cookies for chat and videos. Change your choice any time under Cookie settings. Read our Cookies Policy