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.
Your first results appear 6–24 hours after you connect a cloud environment or install a server agent. 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:
- •Cloud environments — Read-only credentials for each AWS account, Azure subscription, or GCP project. See Minimum Permissions Required for Cloud Connect.
- •Servers — The SeqOps server agent installed on each Windows or Linux server. See the SeqOps Agent Installation Guide.
Why SeqOps Needs It
SeqOps collects and processes metadata only — no customer business data or primary application data. 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 or server appears in SeqOps. For cloud environments, check that the connection status shows as active or valid.
- •Within 6–24 hours — 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
Work through Verifying Your First Successful Scan. 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.