The fit boundary
A narrow migration, not a browser rewrite.
The pilot is for an existing server-side call whose job already matches Latchshot: send one public HTTP or HTTPS URL and receive synchronous PNG, JPEG, or PDF bytes. The repository must be public and under your control.
Fits the pilot
- One existing backend call site in JavaScript, TypeScript, or Python
- One public-page URL on port 80 or 443
- Synchronous PNG, JPEG, or PDF response bytes
- The repository's existing tests and project conventions
Stops the pilot
- Private repositories, private targets, login state, cookies, or customer data
- Scripts, clicks, selectors, scrolling, proxies, CAPTCHA, or browser sessions
- Hosted artifact URLs, provider storage, async delivery, or webhooks
- A new queue, application redesign, extra call sites, or an SLA
If the request hits a stop condition, keep that job on its current provider. The free fit check exists to establish this before money or code changes hands.
The handoff
Four concrete deliverables.
Focused replacement
Replace one agreed provider call while preserving the surrounding application-owned response handling.
Focused coverage
Use the repository's existing test style to cover the request shape, output path, and relevant failure behavior.
Public acceptance sample
Exercise one maintainer-approved public URL and verify the agreed artifact format and dimensions.
Cutover note
Document the configuration change, verification step, and the shortest safe route back to the former provider.
It must stay inside the agreed call site and request contract. New repositories, features, languages, or architectural changes require a separate scope.
The sequence
Fit first. Start only after confirmation.
- 1
Start with the public repository
Email and the exact repository are enough for the free fit check. Add the call site, provider, behavior, volume, or acceptance sample only when you already know them.
- 2
Lock the exact scope
The owner confirms the eligible repository, call site, acceptance sample, and deliverables. Existing Latchshot key holders reuse the same key. If you do not have one, create a Free-plan key only after fit is confirmed.
- 3
Owner confirms payment and start
The owner handles payment separately and explicitly confirms the start. Opening the issue, following this page, or creating a Free key does not take payment or authorize work.
- 4
You review and ship
You retain repository control, review the patch, merge it, deploy it, and decide whether or when production traffic moves.
Done means observable
Tests pass. The agreed artifact arrives.
The pilot is complete when the focused tests pass and the approved public sample produces the required synchronous artifact shape. Latchshot API usage is not included in the $99 fee: use the Free plan for acceptance, then choose a monthly plan only when production volume requires it.
Never include an API key, authorization header, private or signed URL, customer data, payment details, or sensitive artifact in the onsite form or GitHub issue.
The request
Start with the repository. No account required.
Email and one exact public GitHub repository are enough for the owner to inspect the current call site and reply with fit or one specific question. Technical detail is optional and can speed the review. This free request does not take payment, reserve work, create a key, or authorize a repository change.