Questions, answered.

Both - your choice. tday can publish straight to your connected channels the moment an asset is ready, or hold everything in a review queue for your sign-off. You set the policy per channel and can change it any time.

A demo video teaches: an end-to-end, how-to walkthrough of a feature, recorded from your real product. A feature showcase sells: a short promotional cut plus on-brand images, built for social and ads. Every release can produce both.

Either. Connect a GitHub repo and tday runs automatically on every pull request in an isolated sandbox. Or point it at your live or staging site with a demo account and direct which feature to showcase. Both paths produce the same outputs.

With GitHub, yes - every feature that lands in a pull request gets a demo and showcase posted back to the PR. With the website path, you trigger a showcase whenever you want one. Either way, anything can re-run when the UI changes.

Yes. Everything is editable from the platform - rewrite a line of script, swap a scene or thumbnail, regenerate an image, adjust captions - without re-recording the source. Then publish, or send it back to the queue.

Yes. tday applies your colors, logo, fonts, and intro/outro, and the voiceover follows a script you can review and lock. Output is ship-ready, not a rough draft.

If a person can click through it in a browser, tday can. It drives your real product through a standard login, with no SDK or code changes required.

Minutes for a typical feature demo, versus the days a manual edit or an external editor takes.

Point tday at a staging environment or use seeded demo accounts, and connect over OAuth so credentials are never stored in the clear. You control exactly what it can see and record.

Paid campaigns are coming soon. Today tday generates the creative and publishes organically to social; running and tracking paid campaigns from the platform is on the roadmap.