DEV Community

高赫阳
高赫阳

Posted on

I Built ScanInsta: A Browser-Based Instagram Profile Viewer for Public Research

Instagram profiles contain a surprising amount of useful public context: a bio, verification status, follower and following counts, post volume, and recent public content. The problem is that checking this information repeatedly can be awkward when you are doing creator research, competitor screening, or brand-partnership due diligence.

That is why I built ScanInsta, a browser-based Instagram Profile Viewer focused on public information only.

The idea is intentionally simple: enter a public Instagram username and get a clean profile snapshot without logging into Instagram, sharing a password, or installing a browser extension. ScanInsta is designed for people who need fast context rather than another social media dashboard.

What ScanInsta shows

For a public profile, ScanInsta can display the profile photo, display name, bio, verification status, follower count, following count, post count, and recent public posts when they are available. The goal is not to assign a mysterious score to an account. These are background signals that users can interpret in context.

That distinction matters. A large follower count does not automatically mean an account is influential, trustworthy, or a good fit for a campaign. A post count does not tell you whether the content is high quality. ScanInsta simply makes the public profile information easier to review in one place.

Why public data only

I wanted the product boundary to be clear from the beginning. ScanInsta does not claim to reveal private profiles, private followers, private posts, or hidden account information. If Instagram marks something as private, ScanInsta does not try to work around that restriction.

It also does not ask for an Instagram password. For the free workflow, there is no Instagram login requirement and nothing to install.

Who it is for

The most obvious use case is influencer vetting. A brand can quickly review a creator's public profile before deciding whether it is worth doing deeper research or reaching out. Agencies can use the same workflow when screening multiple potential partners.

Competitor research is another use case. Public profile metrics and recent posts can provide a fast snapshot of how actively a competitor is publishing and what kind of content it is putting in front of its audience.

Journalists and PR teams can also use a public profile viewer to collect basic context before outreach. The point is not to replace proper research, but to reduce friction in the first pass.

The stack

ScanInsta is built with Next.js and TypeScript and is deployed as a web application, so the main product experience runs in the browser. I use server-side API routes rather than exposing upstream data-provider logic directly to the client. Redis-based caching and rate limits help control repeated requests, and Cloudflare Turnstile is used as part of the anti-abuse flow.

One of the engineering goals was to keep the initial interaction simple. A visitor should be able to try the product before being pushed into an account-creation flow. The free tier currently supports a small number of daily profile lookups, while higher-volume features such as batch checks, CSV export, profile tracking, and API access are part of the broader product plan.

What I learned

Building a tool around a familiar platform is mostly an exercise in boundaries and reliability. It is tempting to add more promises to make a product sound powerful, but social-data tools are much easier to understand when they are explicit about what they can and cannot access.

For ScanInsta, the product promise is deliberately narrow: help users review publicly available Instagram profile information in a clean browser interface.

The project is available at https://scaninsta.com/.

I am continuing to improve the lookup workflow, caching, rate limiting, and higher-volume research features. If you work in creator research, influencer marketing, competitive analysis, or social media tooling, I would be interested in hearing which public-profile fields are actually useful in your workflow.

Top comments (0)