Think deeper. Move faster. Build bigger.

Talk through the work. Keep the thread.

Ethen Chat is the conversational workspace: choose a model, keep artifacts and sources in one thread, and come back to the work.

1. 01PlanDefine the goal, constraints, and expected outputs.
2. 02CoordinateSeparate research, drafting, and review into bounded passes.
3. 03CheckCompare results with the request and flag missing evidence.
4. 04Keep the recordRetain stage outputs, assumptions, and decisions where supported.

Understand the code. Shape the change.

Bring codebase context, proposed patches, validation notes, and review together. Coming soon.

1. 01Understand a repositoryMap key files, entry points, and open questions.
2. 02Plan a featureScope the change and identify risks and affected files.
3. 03Prepare patch workKeep intent and validation needs with the proposed change.
4. 04Review a diffLook for regressions, edge cases, and missing tests.

Put evidence behind the finding.

A product for defensive security review, triage, and remediation planning with human judgment in charge. Not yet available.

1. 01Review defensivelyInspect available code, configuration, and sensitive application paths.
2. 02Organize findingsRecord scope, evidence, severity notes, and uncertainty.
3. 03TriageSeparate likely issues from questions that need investigation.
4. 04Plan remediationConnect proposed fixes to validation needs and human review.

Give your question room to develop.

Chat Deep Research: ask in conversation, get a sourced report with citations. Fast and limited; the full research workspace is coming.

1. 01Keep the question at the center.Deep Research in Chat moves a question from prompt to sourced report: run, sources, citations, final answer. A full research workspace with projects and evidence tracking is planned.

Choose models with evidence in view.

Compare capabilities, benchmarks, pricing, and evaluations where data is available.

1. 01Compare for the work you need to do.Consider capability, cost, latency, context, and modality where information is available. Evidence coverage varies by model.

Make it in Studio.

Studio is the creative model platform: explore the catalog, generate images and video, compose on canvas, review in cinema, and produce voice. Early access.

1. 01Explore the catalogBrowse models for image, video, audio, and voice.
2. 02CreateGenerate images and video from the workbench.
3. 03Compose on canvasArrange, iterate, and refine creative work.
4. 04Screen in cinemaReview motion and cuts before signoff.

Describe it. Ship the app.

Designer turns a prompt into a working app: UI plus code, with live preview, deploy, domains, and version history. Coming soon.

1. 01Start with a sentence.Describe the app: a page, a dashboard, a workflow. Designer plans it, builds it with integrated coding, and ships it with preview and version history.

Keep the next action in view.

Computer is designed for supervised browser and computer tasks, with visible steps and human control. Coming soon.

1. 01Plan the stepsIdentify the surface, goal, and actions the task may need.
2. 02Review what is visibleDistinguish observations from proposed changes.
3. 03Prepare for reviewKeep form inputs and settings proposals subject to human judgment.

Bring your apps into the work.

Flow is Connected Apps plus approval-gated automation: connect services, use them from Chat tools, and keep every consequential action behind review. Coming soon.

1. 01DraftName the inputs, steps, and expected outputs.
2. 02SimulateInspect a dry run before connecting live action.
3. 03ReviewMark uncertainty and required approval points.
4. 04RepeatKeep the process and its records available for the next review where supported.

One API for supported model access.

Connect your application to supported providers. Configure routing and fallbacks, then inspect requests and usage. Preview — not yet deployed.

1. 01Choose your routesConfigure supported model paths around the task and its requirements.
2. 02Plan fallbacksDefine supported alternatives when a preferred route cannot serve a request. Behavior depends on configuration and availability.
3. 03Inspect trafficReview request logs, route decisions, and usage signals.
4. 04Bring your own keyUse customer-managed provider keys where supported. Provider terms, access limits, and key responsibilities still apply.

Choose where your model runs.

Run supported models locally for code review, internal drafts, and experimentation. Keep the runtime and data path in view. Beta.

1. 01Review codeExplore a local review of unreleased code, then verify the findings.
2. 02Draft internal workRefine notes and plans before deciding what to share.
3. 03Test open weightsCompare model behavior on summaries, extraction, and other repeated tasks.

Your account, orchestrated.

Connect your own provider account. Upcube plans the fit, provisions instances, meters usage, and tears down cleanly. Coming soon.

Give Ethen a job. Get a verified outcome.

Founder is the autonomous-jobs product for company-building work: delegated jobs with approvals and evidence. Coming soon.

1. 01Delegate the job, keep the judgment.Hand Founder a company job: research, outreach, operations. It works the job and returns evidence for review.