Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

The model was the easy part. Maksim Ilin, an AI engineer and consultant, built Dantiva, a photo-to-video product that turns a user’s photo into an eight-second clip with sound, and his first-person account, published September 19, 2026, places most of the hard work in the layer around the model: accounts, one shared token balance, payment correctness, support tooling, and a provider content policy that did not fit his use case. The account describes one founder’s experience. The figures in it are company-reported, not audited, and the market for the product is still unproven.

What Dantiva does

A user selects a template, uploads a photo, and receives an eight-second clip with sound. According to Ilin’s article, video generation used Google Veo 3.1 Fast or Lite. Gemini image models generated and edited pictures, and a separate Gemini model rewrote short user prompts before they reached the video model.

The service runs on three entry points: a website, a Telegram bot, and a Telegram Mini App. All three share one account and one token balance. Around the generation pipeline sit templates, a results library, projects, a legal center available in two languages, and an admin panel that support staff use for handling requests and refunds.

Free tools Windows power users keep installed

One-click scans. No signup required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

A demo that worked but could not be sold

The first version was a Cloud Run deployment that made a single Veo API call and kept its state in memory. As a demonstration it worked. Ilin says it was not ready to sell. Holding state in process memory means that anything the service needs to remember, such as who a user is, what they have paid for, or whether a job is still running, disappears when the process restarts or when a second instance takes over the traffic. Turning that demo into a product meant moving each of those facts into durable storage and building the controls around them.

One identity and one wallet across three surfaces

Each interface authenticates users differently, which is the first complication of running more than one front end:

  • Website: Google sign-in or email verification.
  • Telegram bot: the user’s Telegram identity.
  • Telegram Mini App: a signed Telegram payload that the backend verifies.

Those mechanisms are only the login layer. A purchase made in any one surface has to land in the same wallet, so that the balance a user sees on the website matches the balance in the bot. Ilin introduced a parity check across the three interfaces after a feature mismatch showed that the surfaces had drifted apart.

The clearest illustration came on September 19, 2026. A display bug showed a paid token balance to users who had unlimited access, because a second render overwrote the unlimited status with the balance. Ilin reports that no charge occurred. The screen nevertheless contradicted what the account was supposed to show. The fix was a UI priority rule that decides which status wins when renders collide, plus regression tests that deliberately render twice. His conclusion from the incident is the article’s central line on the subject:

What’s actually slowing this PC down?

Pick the symptom - the matching free tool is one click away.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

“The money logic belongs in one place, and the screens only display it.” (Maksim Ilin, September 19, 2026)

Treating generation credits as a ledger

Ilin describes the token system as a transaction ledger rather than a counter. The flow works in three stages:

  1. Reserve. When a generation job starts, the tokens it will need are reserved against the user’s balance.
  2. Capture. When a result arrives, the reservation is converted into a charge.
  3. Refund. If the provider fails, the reserved tokens are returned.

Idempotency keys guard against duplicate jobs, so that a retried request does not reserve or spend tokens twice. The article also describes three controls that limit exposure: one welcome grant per device, daily ceilings, and limits on concurrent jobs per user. Each of these exists because a paid generation is a stateful operation. A request can fail after money has moved, arrive twice, or come from a user trying to exhaust a free allowance, and the ledger has to answer correctly in each case.

When the provider’s policy changed the catalog

Dantiva’s photo templates depended on recognizable people, the faces of the users who uploaded their pictures. Ilin reports that Veo blocked image-to-video generation with recognizable people in his workflow. He says the filter could not be switched off and that no allowlist was available to him. He continued to use Google models for text-to-video and image generation.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

His lesson is specific to this kind of product. Ilin’s recommendation reads:

“I would test the provider’s content policy on the exact use case before building a whole template catalog around it.” (Maksim Ilin, September 19, 2026)

This is his report about his use case at publication time. It does not establish that every Veo capability or policy context works the same way, and a provider’s rules can change.

Alternatives under evaluation

For photo animation, Ilin was evaluating three other providers. None was connected when the article was published.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Option Status at publication (September 19, 2026) Price per second Other differences the author flagged
Kling, accessed through fal.ai Under evaluation; not connected Not stated in the article Price per second, payment path, and rules affecting Russian users and cards differ between providers
Runway Gen-4 Turbo Under evaluation; not connected Not stated in the article Same axes as above
Seedance, accessed through BytePlus Under evaluation; not connected Not stated in the article Same axes as above

If you are comparing these options for a similar product, the article supports comparing only five things: whether the provider accepts the specific personal-photo use case, what consent or recording requirements apply, the price per second, whether payment is available for your geography, and which provider rules apply to your users. Check each of these against the provider’s current terms, because the article offers no current compatibility assessment and does not name a winner.

Pricing and unit economics

Ilin reported the following plan structure. These are his figures from the September 19, 2026 article, and they reflect the prices he published at launch.

Plan (as named in the article) Price (rubles) Tokens included
Start subscription 199 1,400
Author subscription 499 4,200
Pro subscription 999 10,080

Small token top-ups began at 99 rubles. One eight-second Fast video with sound cost 140 tokens. Ilin put the cost of producing an eight-second clip at roughly 80 rubles at Google’s list price, and he said the catalog was normalized to around 30% gross margin at real provider prices. Subscriptions launched September 18, 2026.

Those margin figures need to be read with the subsidy in view. Ilin said a Google Cloud grant subsidized generation, and that he expected to evaluate the economics after the grant ended in November. Until observed usage replaces the grant-supported costs, the margin should be treated as a working hypothesis. The reported cost, the subsidy, the realized utilization of plan credits, and the plan prices all interact, and the article does not provide enough data to isolate any one of them. Do not compute a standalone margin from the headline figures.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Naming a product mid-build

The customer-facing name changed from Project Aurora to Synora and then to Dantiva. The internal identifiers stayed Synora. Ilin kept the internal service and environment names because renaming them would have meant a risky migration with no customer-facing benefit. That was his decision for this system. It is not a general rule against renaming, and he says he would choose the final name sooner next time.

Who it is for and what is still unproven

Ilin describes an intended Russian-speaking audience that wants videos featuring themselves, such as birthday greetings, social-media trends, and avatars. The advantage he said he could substantiate is ruble payment through Telegram with a receipt. He explicitly calls the broader segment a hypothesis.

A later update from the author reports that one customer completed the purchase path, including a monthly subscription in the Mini App. The same update states that this does not establish repeat retention, a stable acquisition channel, or product-market fit. It should be read as a single dated data point, not as proof that the original uncertainty has been resolved.

What Ilin says he would do differently

  • Check the provider’s content rules against the precise intended workflow before building the template catalog.
  • Write the ledger before the screens.
  • Choose the final product name sooner.
  • Ship subscription pricing earlier to learn more about demand.

These are his recommendations, drawn from his own build. They are not tested against other products.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.