Profile once. Matched postings from employer career sites. An ATS-ready Lebenslauf and Anschreiben per posting. You approve every application; nothing is sent without you.
kelyvaro.com · Turkish & English · Germany first
Turkish job seekers — welders, electricians, truck drivers, nurses, cooks, engineers — usually pay an intermediary thousands of euros up front to reach a German employer. Kelyvaro is the tool instead of the intermediary.
| Step | What happens |
|---|---|
| Profile | Target country, occupation and German level open your list in under a minute; the rest is only needed for the CV. |
| Matching | Postings from Adzuna and employer applicant-tracking boards (Personio, SmartRecruiters, Greenhouse, Workday, Oracle, softgarden …) are scored against your profile — with the reasons shown, not just a number. |
| CV & letter | For each posting, a German tabular Lebenslauf and a DIN 5008 Anschreiben are generated. The model drafts from profile facts; structured output and grounding checks run before preview. |
| Sending | The mail goes from your own Gmail (send-only permission). It stays in your Sent folder; the employer replies to you. |
| Tracking | Sent applications and user-recorded outcomes in one place; replies stay in Gmail. |
No job guarantee, no placement, no hidden fees. The first application is free; then a single monthly payment, no auto-renewal.
 |
 |
| Matches. Every row explains why it fits; a four-step guide walks a new user to the first free application. All traffic is mobile, so the mobile layout is the primary one. | |
 |
 |
| Dashboard. Profile strength is the only score shown — it is computed, not decorative. | CV studio. Missing inputs are listed before anything is generated. |
 |
 |
| Guides. Seven guides on German CVs, recognition (Anerkennung), the EU Blue Card and the Opportunity Card — including a points calculator built from the text of the law (§20a/§20b AufenthG). | Mobile dashboard. |
Occupation index. 46 occupations with verified requirements (recognition, visa route, salary thresholds) and live posting counts.
- Next.js 15 (App Router, TypeScript strict) · Tailwind v4 · next-intl (tr/en)
- Supabase (Postgres, RLS on every table, pg_cron) · Vercel (Frankfurt region)
- Job sources: Adzuna API, Arbeitnow, and an employer ATS registry; the generic discovery and reader layer is open-sourced as ats-boards (12 providers)
- Generation: Groq-hosted open-weight model with structured JSON output; profile-grounding checks before preview and prompt regression tests with promptfoo
- Sending: Gmail API with the least-privilege
gmail.sendscope; an MX preflight checks recipient-domain mail routing before send - Measurement: GA4 + Meta CAPI + PostHog (EU), all behind explicit consent
- Video: launch spots rendered with Remotion from the same design tokens as the site
Design language is editorial rather than "SaaS template": Newsreader headings, Inter body, ink-and-paper palette, lines instead of cards, one accent used sparingly.
The core engineering constraint is trust: an application contains personal career data, AI-generated language and an outbound message in the user's name. Kelyvaro automates discovery and drafting, but keeps identity, approval and final sending under the user's control.
flowchart LR
subgraph U["User trust boundary"]
B["Browser<br/>profile, review, approval"]
end
subgraph K["Kelyvaro trust boundary"]
W["Web app & server routes"]
D[("Postgres<br/>RLS-protected rows")]
I["Job ingestion<br/>& normalization"]
M["Explainable matching"]
V["Draft orchestration<br/>schema & fact checks"]
S["Send controller<br/>approval & MX preflight"]
end
subgraph T["Third-party trust boundaries"]
J["Public job APIs<br/>& employer ATS boards"]
L["Hosted language model"]
G["User-authorized Gmail<br/>gmail.send only"]
E["Employer mail server"]
A["Analytics providers"]
end
B <--> W
W <--> D
J --> I --> D
D --> M --> W
D --> V
V <-->|"structured draft"| L
V -->|"validated preview"| W
B -->|"explicit approval"| S
S --> G --> E
W -. "only after consent" .-> A
| Decision | Guardrail | Trade-off |
|---|---|---|
| Keep a human in the send loop | Every generated document is previewed; sending requires explicit approval | More user effort, but no autonomous application in the user's name |
| Treat the profile as the factual source of truth | Structured output is checked against profile data before preview; prompt regressions are tested | Conservative copy and occasional regeneration instead of silently accepting unsupported claims |
| Isolate user data at the database boundary | Row-level security is enabled on every application table | More policy and test maintenance, stronger defence if an application query is wrong |
| Ask Gmail only for send access | gmail.send can send the approved message without inbox-read permission |
Replies remain in Gmail and outcome tracking cannot depend on reading the inbox |
| Prefer source fidelity over invented completeness | ATS readers normalize only fields returned by public employer boards and use conservative Germany filtering | Some incomplete postings remain incomplete or may not match as strongly |
| Measure only after consent | Product and marketing analytics are gated behind an explicit choice | Less complete funnels in exchange for a clearer privacy boundary |
An MX result only confirms that a domain publishes mail-routing records; it is a preflight, not a guarantee that a mailbox exists or that delivery will succeed.
I own Kelyvaro's product and engineering lifecycle: product/technical direction, application architecture, data model and RLS policies, job ingestion and explainable matching, generation guardrails, Gmail send flow, responsive UX and localization, deployment and production operation. My co-founder owns distribution.
- Live beta and the repository's matching, CV studio and mobile captures document the shipped user flows.
- ats-boards contains the reusable ATS discovery/reader layer, provider verification notes, normalized posting contract and offline tests.
- Repository history records the evolution of this public showcase.
The production repository and customer data are private. This diagram deliberately shows responsibilities and trust boundaries, not secrets, internal endpoints or deployable implementation details.
Live beta since August 2026. Built and operated by Murat Sert; a co-founder leads distribution.
Screenshots use a sample profile ("Mert Aydın"); no user data is shown.
© 2026 Kelyvaro. Screenshots and text in this repository are provided for reference only (see LICENSE).