VinDevs Services

Packages

LiveOps Support

Regular monthly help for an experience that is already running.

Ideal for A live game that needs steady content, seasonal events, and someone on hand when something breaks on a Saturday.
Team Reserved developer or pair
Expected duration Monthly
  • Luau scripting
  • Live incident response
  • Event and content design
  • Economy and balance
  • Data and analytics

What you get

Everything below is written into the proposal before you fund anything.

  • A named developer or pair reserved for your experience each month, with agreed working hours.
  • A monthly content plan agreed with you, covering events, balance passes, and fixes.
  • A response time for live incidents, written into the agreement rather than left implied.
  • A monthly written report of what shipped, what broke, and what should be next.
  • Continuity: the same people, so nobody re-learns your codebase every month.

What is not included

Stated up front so any disagreement about what is included happens now rather than at delivery.

  • Nobody is on call outside the agreed hours.
  • No community moderation or player support.
  • Not a replacement for a technical owner. Someone on your side still makes product decisions.
  • Not available as your first project with VinDevs. We plan it after we have delivered one.

How delivery runs

Expected duration for this package is monthly, measured from the point the project is funded rather than from the brief.

  1. First project

    LiveOps Support follows a delivered Fix Sprint, Feature Pod, or Launch Squad, so both sides know the codebase.

  2. Monthly plan

    We agree in writing how much work happens each month, the working hours, and how quickly we respond to incidents.

  3. Monthly cycle

    A plan at the start of the month, work in the deal room through it, a written report at the end.

  4. Review

    Every month is a decision point. You can ask for more, ask for less, or stop, with no penalty.

How your money is protected

This package runs as a protected deal. Your money is held by VinDevs, not paid to the team up front, and is released after you approve delivery.

  1. Approve the plan first

    Nothing is charged until you have read the proposal, seen who is on the team, and agreed the milestones and the price.

  2. Funds are held, not sent

    You fund the project once the plan is agreed. VinDevs holds the money: the team can see it is funded and starts work, but cannot withdraw it.

  3. Delivery happens in the open

    Work, files, and progress are sent to you in a shared deal room. You approve a milestone, ask for changes, or raise a dispute, and VinDevs dispute staff can read the whole record.

  4. A protection window before release

    Funds stay protected for 7 days after you approve delivery, so a problem you find afterwards is still covered.

  5. Disputes are handled by staff

    If you and the team cannot agree, VinDevs dispute staff review the deal room and decide. A dispute pauses the release until it is resolved.

Common questions

Why can we not start here?

A monthly price set before anyone has read your codebase is a guess. One delivered project makes the number honest.

Is there a minimum commitment?

One month. Each month is renewed by choice, and the agreement states the notice period for stopping.

What counts as a live incident?

The agreement defines it explicitly, usually a break that stops players progressing or loses data. Nothing is left to interpretation.