How SILKTRACE
is built.
How reports stay private, saved results stay useful, and paid research stays under your control.
Every request.
A deliberate path.
Reading a report and running new research take different routes. Choose a path, then inspect each step.
Resolve ownership
The server resolves your signed-in account and its workspace before reading private reports.
The details you
shouldn’t have to think about.
Good engineering makes the boundaries predictable. These decisions shape the experience of every report.
Evidence before interpretation
Reports use consistent view models, with clear missing-data states and labeled provider estimates. Unavailable evidence stays unavailable.
Your credentials stay on the server
DataForSEO credentials are encrypted with a server-only keyring. Your browser does not receive the saved provider password.
Reading stays separate from spending
Report navigation reads stored evidence. New provider work requires an explicit protected action, with cost confirmation at the applicable threshold.
A refresh keeps its history
Technical refreshes retain the last successful snapshot while new work is running or when a refresh fails.
A considered foundation.
Each layer has one responsibility, from the interface to the provider boundary.
- Interface
- Next.js 16, React, TypeScript
- Storage
- Neon PostgreSQL
- Identity
- Google sign-in through Neon Auth
- SEO evidence
- DataForSEO
- Application hosting
- Vercel
Care that goes
beyond the interface.
Type checks, unit tests, runtime smoke tests and security regression tests examine different layers of the application.
SILKTRACE is privately maintained. Application source is proprietary.
Back to the productGet a feel for
the whole picture.
Free application access.
Live data is billed separately by DataForSEO. How access works