Turn a sentence into a web or mobile app, a CV, a presentation or a month of social posts — planned with you, made by one agent, paid from one credit wallet.
Try:
500 free credits every month · No credit card needed
Native iOS and Android apps, or a web and mobile twin.
Explore Mobile apps
Maya Chen
Senior backend engineer
Backend engineer with nine years of experience building reliable payment and data platforms used by millions of people. I like simple designs, measurable results and growing the engineers around me. Looking for a staff-level role where reliability and developer experience matter.
Experience
Senior backend engineer
Mar 2021 –Present
Northwind Pay · San Francisco, CA
Led the move to an event-driven ledger, cutting settlement time from four hours to six minutes
Reduced p95 API latency by 38% through query tuning, connection pooling and caching
Designed the idempotency layer that ended duplicate charges across 40 million monthly payments
Mentor five engineers and run the backend guild’s design reviews
Software engineer
Jun 2017 –Feb 2021
Brightline Data · Seattle, WA
Built ingestion services that process 2 billion events a day on Kafka and Go
Introduced contract tests that halved production incidents within two quarters
Cut cloud spend by $410k a year by moving cold data to tiered storage
Junior developer
Jul 2015 –May 2017
Cascade Health Tech · Seattle, WA
Shipped the appointment API used by 120 clinics
Automated release checks, taking deploys from weekly to daily
Education
B.Sc. Computer Science
2011 –2015
University of Washington · Seattle, WA
Capstone: a fault-tolerant queue for campus transit data.
Projects
pgwatch-lite
Open source
A small PostgreSQL health dashboard with 2,300 GitHub stars, used by teams at three fintechs.
Volunteering
Mentor
Jan 2019 –Present
Code Bridge SF
Weekly mentoring for career changers learning backend development; 14 mentees hired as engineers.
App demos run the template’s own screens with sample data; when you start from one, the agent writes, tests and previews your own app. CVs, decks and posts are documents made with Craftkite.
How it works
Five steps from idea to live app
1
Step 1 of 5
Describe
Write, say or sketch what you need, in your own language. Add screenshots of anything you like.
Describe your app
A booking app for my yoga studio with a waitlist
2
Step 2 of 5
Approve the plan
The agent asks back when something is unclear and shows screens, data and the credit estimate. Nothing runs until you say OK.
Plan ready · waiting for your OK
Class schedule with day and week views
Waitlist when a class is full
Email sign-in for members
Database: classes, bookings, members
6 screens · 2 tables · ≈ 300 creditsApprove plan
3
Step 3 of 5
Build
The app is written file by file in an isolated sandbox, with a database and sign-in when it needs them.
app/page.tsx
app/schedule/page.tsx
app/api/bookings/route.ts
lib/db/schema.ts
components/class-card.tsx
14 files written
4
Step 4 of 5
Test and repair
A real browser clicks through the app. When a check fails, the agent fixes it and tests again.
12 of 12 checks passed
5
Step 5 of 5
Publish
On a paid plan, one click puts it live with HTTPS on a Craftkite address or your own domain. Keep improving it by chatting.
lotus-yoga.craftkite.app
Live in 1m 42s
Describe your app
A booking app for my yoga studio with a waitlist
Plan ready · waiting for your OK
Class schedule with day and week views
Waitlist when a class is full
Email sign-in for members
Database: classes, bookings, members
6 screens · 2 tables · ≈ 300 creditsApprove plan
The agent at work
It doesn’t just generate. It checks its work.
Every task runs through the same loop, and you can watch each step as it happens.
Plan approval
A clear plan of screens, data and integrations, with the credits it will take. You approve, edit or cancel.
Browser testing
The tester opens your app in a real browser, clicks through the main flows and checks every screen.
Self-repair
When a test fails, the agent reads the error, fixes the code and runs the tests again — at no extra credit when the failure is ours.
Live logs
Every file, command and test result streams to the studio, so nothing happens behind your back.
Live log
00:04✓plan approved · 6 screens · 2 tables
00:16›sandbox ready · dependencies installed
00:29›write app/schedule/page.tsx
00:41›write app/api/bookings/route.ts
00:53›browser test · booking flow
01:05✕check failed · button hidden on small screens
01:18✓repair · layout fixed
01:30✓browser test · 12 of 12 checks passed
01:42●published · https · 1m 42s
languages for the studio, the agent and your apps
0languages for the studio, the agent and your apps
steps on every task: plan, build, test and repair
0steps on every task: plan, build, test and repair
test scenarios in the agent’s quality set
0+test scenarios in the agent’s quality set
minutes, typically, from a prompt to a tested preview of a simple app
0minutes, typically, from a prompt to a tested preview of a simple app
Publish and own
Ship it anywhere. Keep every line.
Your app goes live in one click — and the code stays yours to take wherever you want.
Your own domain
On a paid plan, verify with one DNS record and get HTTPS automatically.
app.yourcompany.comDNS verified · HTTPS
ZIP export
On a paid plan, download the full source code at any time. No lock-in.
source.zip
Your app
GitHub sync
On a paid plan, push every version to your repository automatically, or pull changes back.
Version pushed to main
App Store and Google Play
From the Builder plan up, publish the mobile apps you build to your own App Store and Google Play accounts with the store wizard.
App StoreGoogle PlaySubmitted for review
Security and trust
Safe by default, honest by design
Protections in place on every account, from day one.
In place
Isolated sandboxes
Every app is built and run in its own isolated sandbox with restricted network access.
In place
Encrypted secrets
API keys are stored encrypted in your vault and checked for leaks before anything is published or pushed.
In place
Audit trail
Sensitive account and admin actions are written to an append-only audit log that can be exported.
In place
GDPR and KVKK
Export your data or delete your account at any time. A data processing agreement is available.
In place
No training on your work
Your prompts and code are never used to train AI models.
In place
SOC 2 controls
Access control, encryption at rest and in transit, an append-only audit trail and mandatory two-factor sign-in for staff, built to the SOC 2 Type I criteria.
No. You describe the app and approve the plan. If you do code, you can open the editor at any time and change anything.
Who owns the apps I build?
You do. The code is yours to change, sell and host anywhere, including outside Craftkite; downloading it and syncing it to GitHub come with a paid plan.
What is a credit?
A credit pays for a share of the AI and computing work behind a task. A change usually takes 50 to 350 credits and a new app 400 to 1,600. You see the estimate before anything starts.
Is my data used to train AI models?
No. We do not use your projects or prompts for training, and neither may the AI partners that power the Craftkite engine.
Can I use my own domain?
Yes, on a paid plan. Add your domain in the Publish tab, set one DNS record, and your app is served there with HTTPS.
Can I cancel anytime?
Yes. Your plan stays active until the end of the paid period, and the free plan remains.
Can Craftkite build anything?
Craftkite builds websites, web apps and iOS and Android apps. For very large systems such as an ERP it builds the core and the code is yours to finish on GitHub. Desktop programs and games that need a game engine are not supported yet; the planner tells you before you spend credits and suggests the closest option.
Can Craftkite make more than apps?
Yes. Besides web and mobile apps, the same agent writes CVs, presentations and social media content. You choose what to make in the prompt box.
Do apps and documents use the same credits?
Yes. One credit wallet pays for everything you make. Apps have a typical range measured from real tasks; document actions have a set price. You see it before anything starts.
Which languages does Craftkite speak?
The studio, the agent and its plans work in English, Turkish, German, Spanish, Brazilian Portuguese, French, Japanese and Hindi. The apps you build can support several languages too.
Can I publish mobile apps to the App Store and Google Play?
Yes, from the Builder plan up. Craftkite builds native iOS and Android apps, and the store wizard builds them for you and publishes them to your own Apple and Google developer accounts.
What happens when the agent makes a mistake?
The tester catches most problems in a real browser and the agent repairs them before you see the result. You can also undo any change by restoring an earlier version.
Can I connect services like Stripe or my own AI keys?
Yes. Ask for the integration in your prompt and add your keys to the secret vault. They are stored encrypted and never written into the code.
Can my team work together?
Yes. The Team plan adds workspaces with shared projects, roles, invitations by email, one shared credit pool and single sign-on.
Where are my apps hosted?
On a paid plan, published apps run on Craftkite with HTTPS on a Craftkite address or your own domain, and you can export the code and host it anywhere you like. On the Free plan you preview your apps before you publish.
Is there a Craftkite app for my phone?
Yes — the Craftkite mobile app for iPhone, iPad and Android is on its way to the App Store and Google Play. It lets you start builds, approve plans and get notified when your app is live.
How do you keep my projects safe?
Every app runs in an isolated sandbox, secrets are encrypted, sensitive actions are logged and your work is never used for training. You can export or delete everything at any time.
Ready when you are
Your next idea is one sentence away
Create a free account and make your first app, CV, deck or campaign today.
