Joined May 2026
- Tweets 39
- Following 0
- Followers 23
- Likes 0
39 Photos and videos
No Docker. No config files. No environment variables.
No server bill at the end of the month.
With ember you never see the infrastructure, because handling it is our job, not yours.
You just see your project, live.
13
12h
The word "vibe" does a lot of work. "Minimal," "playful," "brutalist," each pushes the design somewhere specific.
Pick a style and it falls into place.
2
36
Jun 14
Agents that run on their own, all day, are coming for everyone.
The question nobody's answering is where they'll actually live.
ember is being built to be that home: describe an agent, and it runs, hosted, on its own.
52
Jun 14
ember doesn't hand back a first draft.
It reads your files, makes the change, checks its own work, and fixes what it gets wrong, before you ever see it.
What lands is finished.
38
Jun 13
A job board with no backend to babysit.
"A remote design jobs board, simple listings, easy to post."
Built and hosted, nothing to manage.
Pick a niche and it's live, collecting posts.
63
Jun 13
Shipped something you don't love? Go back in one click.
Every version you publish is kept intact, so rolling back is instant and nothing is ever lost.
Your history is your undo button, and it's always there.
3
42
Jun 12
Video generation is inside ember.
Describe the clip, watch it resolve, and it lands in your build as a live background video.
No editor, no stock libraries, no export step.
One prompt. Done.
1
86
Jun 12
Give your community one place to look: a dashboard with live counts, links, and a feed, built from a sentence and hosted on its own address.
The whole frontend, described into being.
44
Jun 11
Two ways to build:
Making safe, conservative changes because you can't afford to break it.
Or trying the bold version because you can rewind to any point automatically.
ember is the second.
1
54
Jun 11
Everyone wants to demo the magic: prompt in, product out.
Nobody wants to talk about the hosting, the isolation, the security.
That unglamorous part is the part we built first.
2
57
Jun 11
A tip for using AI:
When something feels off, don't fix everything in one message. "The hero's wrong, the colors are cold, the cards are confusing" gets a confused response.
Pick the biggest problem, fix it, move on. One at a time wins.
1
33
Jun 10
Two build experiences:
Spending hours wiring up a database before you write any code.
Or saying "add a database to store signups" and moving on.
ember is the second.
Which one do you prefer?
3
40
Jun 10
Try the bold version. If it misses, you're one step from where you were, because ember saves every iteration as you go.
There's no way to lose work, so there's no reason not to experiment.
3
53
Jun 10
With ember you never have to see the infrastructure,
because handling the complex part is our job, not yours.
You just see your project, live.
1
3
4
64
Jun 9
One prompt in.
A finished blog out.
No drafts. No proofreading. No waiting.
Describe the post you want and ember writes the whole thing, then publishes it for you.
What would you have it write first?
3
64
Jun 9
This is what generating on ember looks like:
Describe the image, pick a model, and see the cost in sparks before you commit.
No surprise bills, no credit-card roulette. Just a prompt, a price, and a result.
1
3
71
Jun 9
Keep your users in the loop without building a thing.
"A public roadmap and changelog site, clean and simple."
Describe the vibe, ship it, and update it later just by chatting.
3
2
5
97
Jun 9
Projects you're not using shouldn't cost you.
On Ember an idle project quietly suspends and uses nothing, then wakes on the next visit in a second.
You pay attention to your ideas, not to a meter ticking in the background.
3
2
4
79
Jun 8
There's a quiet line being drawn in this space. On one side, tools that generate something and hand it to you.
On the other, platforms that generate it and then run it.
ember is the latter, we build it, and run it for you.
3
65