Morning brief
Start the day already caught up.
Check analytics, market changes, important conversations and blockers. Kryx returns the few things worth your attention.
“What changed overnight that I should care about?”
Kryx · the founder's agent army
Give Kryx a goal. It researches, plans, works across your tools and devices, asks when a decision is yours, and brings back finished work instead of another chat transcript.
No workflow builder. No agent setup screen. No monthly seat fee.
Give Kryx a job
Example mission
Find 20 SaaS founders who could need Kryx, qualify them, and prepare personalized outreach.
Try asking
The actual founder problem
Most AI makes the founder responsible for routing, prompting, copying context and checking whether anything actually happened. Kryx is built around the opposite idea: give it responsibility for the job, then step in only when your judgment matters.
Ask one AI to research, another to write, copy context into a third tool, then remember what still needs doing.
A useful agent should keep moving the job forward, not hand the founder another half-finished document to manage.
The moment an agent can touch your browser or apps, you need clear boundaries, receipts and approvals — not blind autopilot.
What founders hand to Kryx
Not twenty agent portraits. Not twenty chats. You talk to Kryx; Kryx decides which specialist skills and execution path the job needs.
Morning brief
Check analytics, market changes, important conversations and blockers. Kryx returns the few things worth your attention.
“What changed overnight that I should care about?”
Growth
Research conversations, prepare content, find leads, qualify them, update sheets and keep launch work moving.
“Promote this launch today and bring me the work to approve.”
Founder ops
Work with docs, inboxes, spreadsheets, browsers and approved desktop or Android apps without rebuilding every workflow as an API integration.
“Open the sheet, update the qualified leads and summarize what changed.”
Research
Kryx can investigate companies, products, customers, markets and competitors, then bring back sources with the conclusion.
“Research these three competitors and tell me what changed this month.”
Communication
Draft messages, posts and follow-ups from real context. External actions can wait in Needs You until you approve them.
“Read the relevant thread and draft the reply I should send.”
Recurring work
Schedule research and reporting, or let Observer Mode detect a repeated routine and propose what Kryx could automate safely.
“Every weekday, prepare my competitor brief before I start work.”
Five phases, one conversation
Kryx keeps the machinery behind the scenes. You see the plan, real progress, decisions that need you, and the final receipt.
Tell Kryx the outcome in plain English. No workflow builder.
Kryx picks the smallest useful set of skills, tools and devices.
Independent steps run in parallel where that is safe and useful.
External or consequential actions stop for your decision.
Finished work comes back with sources, actions, cost and blockers.
The army is capability, not characters
The founder should never have to decide which bot to open. Kryx assembles the useful skills behind one mission and returns one coherent outcome.
Market research, competitor tracking, customer signals, analytics and synthesis.
Content, search, distribution, landing pages and conversion work from real founder context.
Find the right people, qualify fit, prepare outreach and keep the pipeline organized.
Inbox, docs, meetings, spreadsheets, browser work and approved device actions.
Works where the work already lives
Kryx can research in the cloud, use your real signed-in browser, and run approved local work on Mac, Windows, Linux or Android. The execution method is part of the plan — not something you wire by hand.
Planning, research, model work and public web tasks.
Use the browser session you are already signed into.
Approved local app, file and accessibility-driven work.
Use structured APIs and tools when they are the safer path.
You can loosen a rule after you trust a workflow. Kryx should never silently increase its own permissions.
Research, inspect public pages, analyze data and prepare drafts can run with low friction.
AutomaticSending, publishing and editing external systems can stop in Needs You first.
Ask firstPayments, destructive deletes, passwords and account-security changes remain blocked or explicitly human-controlled.
RestrictedPersistent, not forgetful
Workspace memory keeps the facts that make future work useful: product, ICP, tone, approved claims, rejected language, campaign outcomes and the rules you set for your devices.
Products, positioning, pricing, competitors and workspace context.
Voice, corrections, rejected phrases and patterns you keep choosing.
Allowed apps, approval policies, exclusions and autonomy per workflow.
What performed, what failed, what was approved and what should not repeat.
Docs that explain the product
Quickstart, missions, devices, approvals, credits, Observer Mode, scheduling and privacy — written for founders, not infrastructure teams.
Read the docsCreate your workspace, give Kryx one real job, review the receipt.
Use the same account on Android, Mac, Windows or Linux.
Choose what runs automatically and what always waits for you.
Schedule work or turn a repeated routine into a proposed automation.
Pay for work, not another seat
New accounts start with 100 credits. Credits are consumed by billable model/tool work; local clicks do not exist just to burn your balance.
Try it
$5
500 credits
Founder
$25
2,500 credits
Heavy use
$50
5,000 credits
Example costs: draft 5 · web search 6 · lead search 30 credits.
See every costFAQ
Kryx is a founder's agent army. You give it the job, not a workflow diagram. Kryx decides which specialist skills, tools and execution surface the work needs, then brings back the result and the decisions that still need you.
Marketing and growth remain strong parts of Kryx, but the product now also covers founder operations such as research, inbox triage, docs, meetings, spreadsheets, browser work and approved device actions.
No. The default experience is one Kryx. It can assemble research, growth, pipeline and founder-operations skills behind a mission without making you manage separate agent chats.
Yes, when a task needs local context and the device is connected. Kryx can use approved browser or device capabilities while keeping the same account, credits, missions and approvals across web and device apps.
External actions use separate approval policies. Research and drafts can be low-friction; sending, publishing or editing an external system can wait in Needs You. Sensitive actions such as payments, destructive deletion and account-security changes remain restricted.
It should be narrow. For example, you can allow Kryx to open a specific app in future missions without granting unrestricted authority to send, publish, delete or change security settings inside that app.
Kryx uses prepaid credits rather than a monthly seat in the current offering. New accounts start with 100 credits. Billable model/tool work uses credits; local clicks are not charged just for existing.
No model key is required to start the hosted product. Kryx uses its configured provider routing and failover. A connected third-party service may still have its own permissions or limits.
It should surface the exact blocker — for example a login, CAPTCHA, missing permission, unavailable device or changed interface — instead of pretending the work completed.
No. Observer Mode is optional and explicitly enabled. It is intended to capture structured workflow metadata in allowed apps so Kryx can propose repeated routines for automation, not to keylog passwords or private text.
Stop managing your AI.