What we believe.

We love computers, and question what they've become for kids. So we talk to parents, read the research, and build a first computer worth growing up with. Daso is that computer: a calm, capable machine for ages 6–12. This page is the thinking underneath it.

Richard Feynman liked to tell a story about his father. Other fathers taught their sons the names of birds; his pointed at one and said that the name tells you nothing about the bird. Watch the bird, he said. See what it's doing. That instinct, that observing beats naming, is the seed Daso grows from.

So when a kid asks Daso a question, the AI doesn't just hand back an answer, pull up a source, or volley a follow-up question. It opens a door. It leads with the part worth wondering at, the “wow,” and then offers a few honest ways to find out more: watch it, test it, map it, tell it. The kid picks the path, and the picking matters, because choosing is where agency lives. A good session ends with more questions than it started with, and the new questions point outward at the world, not back at the screen.

None of it is a shortcut. We never switch a kid into creative mode, because the fun of building lives in the struggle, the way diamond armor means something because you hunted for it. Progression on Daso is earned by making things, not by streaks, points, or login rewards. Real capabilities unlock as a kid demonstrates they're ready for them: more tools, more reach, a longer leash. And the ladder is visible. Kid and parent can both see what Daso currently believes the kid is ready for, and why, and can change it. The AI may perform a story as written or run the code a kid dreamed up, and it may make a question bigger, but it never makes the thing for them.

Nothing starts from a void, either. Every project begins from a remixable seed: a half-built story, a simulation that bends when you poke it, another kid's creation. Projects stay out on the bench where you left them, easy to return to and build on, and completely inert. Nothing on Daso animates itself, suggests, or is “new for you.” The kid starts every session. Real tools are in there too, a notepad, a camera, a movie maker, a music maker, real code, and a kid discovers them the way you discover a hammer: by needing one. What they make stays theirs, and over time their artifacts become a record of what they were curious about, for kid and parent both.

The AI's strongest move is declining to answer. Some questions deserve a person: “This sounds like a dad question. Want me to save it for him?” Daso is built to spin kids outward toward the people around them, never to become the relationship itself. Parents choose the circle, and inside it kids can send what they made, read together, or take on a puzzle with someone they love. We count it as a win every time a kid talks to Daso less and to people more.

For parents, Daso is leverage, not homework. It sends you short notes about what your kid is exploring and making, with real ways to join in: a game to play, something to do together away from the screen, or just the chance to admire the thing they built. Say “she needs fraction practice” and it reaches your kid as a quest. Share the co-op packet and it arrives as itself, openable and completable, labeled “From Mom.” Everything is safe from the moment the box opens, and the settings read like plain language, not an afternoon of menus.

All of this runs on trust, and we believe the burden of proof is ours in every interaction. So we make our behavior checkable instead of asking you to take our word. You can read what Daso remembers about your kid, edit it, export it, or delete it. We follow COPPA strictly. We name the AI models we use, where they run, and what they're for. Nothing enters Daso's catalog except by a family asking for it, money flows from parents to creators and never from creators for placement, and no partner ever sees engagement analytics.

And we keep one number in front of ourselves to stay honest: things made versus minutes consumed. We watch it; we never optimize it. If Daso is working, a session ends with a kid leaving the screen with a question in hand. A computer, not a companion.