01Base
Lay the base
Bring in repositories and/or service accounts through reusable provider connections.
See your software
The agent translates your code into a living architecture map
Connect your codebase and services
See flows in your architecture
Identify flows in the system
Step by step backed by code
Refine, ask, inspect, repeat
01Base
Lay the base
Bring in repositories and/or service accounts through reusable provider connections.
02Ask
Ask the agent
Ask the agent to inspect the codebase and propose nodes, edges, and source evidence.
03Map
Update the map
Accept the agent change suggestion.
04Review
Review the system together
Refine the map, attach live service context.
Review loops back to Ask the agent.
One workspace connected to your services
The map becomes more useful as the real system connects.
GitHub
Connect your repositories and manage code
Vercel
Deploy and manage your applications
AWS EC2
Elastic compute cloud instances
AWS S3
Object storage and file management
Stripe
Payment processing and billing
Lemon Squeezy
Store analytics and subscription metrics
Clerk
Authentication and authorization
Systems Manager
Configuration and secrets management with Parameter Store
IAM
Identity and access management for AWS resources
Sketch the system first, even before the codebase is connected.
Still works as a clean architecture canvas
Privacy by design
Useful signals, without your workspace content.
Scalink uses PostHog Cloud EU for cookieless public page views and, after affirmative consent, limited authenticated product events and content-free AI generation measurements. Public analytics creates no person profile and can be disabled from the privacy page.
Explicit consent
Product Telemetry stays off until an authenticated user allows it. Declining does not block Scalink, and the preference can be changed later in Settings.
No workspace content
Prompts, responses, tool contents, reasoning text, diagrams, repository names or URLs, workspace names, emails, provider account data, and raw errors are never sent as Product Telemetry.
No behavior recording
Session replay and autocapture stay disabled everywhere. Public analytics is limited to cookieless page views; authenticated Product Telemetry excludes URLs, paths, and referrers.
Privacy-preserving context
Events use opaque identifiers and fixed property allowlists. AI telemetry is limited to model, usage, exact cost, timing, status, and controlled errors. Eligible browser events retain only an approximate country code, and the IP address is discarded after derivation.
Zero Data Retention for AI requests
AI requests use OpenRouter Zero Data Retention routing with provider data collection denied. Model providers do not retain prompts or responses or use them for training; OpenRouter may retain operational metadata such as token counts and latency.