Skip to content
How we work
Start a conversation Talk to us

For products left without a developer

Keep your live product running after your developer moves on

Ongoing support for a web application means someone takes responsibility for it after launch: learning how it is built, keeping hosting, dependencies and patches current, fixing what breaks and improving it in agreed steps. The scope, access and escalation are written down first.

Free first conversation · A person replies within one business day · You own the code and accounts

01 Sound familiar

Sound familiar?

  • The person who built your application has moved on, and nobody else knows how to deploy it or where the passwords live.

  • A small bug has sat unfixed for weeks, because changing anything feels risky without the original developer.

  • Hosting bills, expiring certificates and security warnings arrive by email, and it is not clear whose job they are.

Who owns what

See who owns what, week by week

Pick a shape. The lanes show how the first weeks typically split between you and us; the actual plan and its pace are agreed with you before support begins.

Take over and stabilize

  1. Week 1

    You
    Grant access to the code, hosting and domains, and tell us how customers use the product.
    Nexstella
    Take inventory of the code, hosting, accounts and deployments, and note what is fragile or undocumented.

  2. Week 2

    You
    Confirm which features matter most to your customers and which known bugs hurt.
    Nexstella
    Make deployments repeatable, move secrets into a safe store and fix the most urgent issues.

  3. Week 3

    You
    Read the handbook we write and agree how you want to raise requests.
    Nexstella
    Document how to run, deploy and restore the application, and add monitoring for the parts customers use.

  4. Then each week

    You
    Raise requests and set priorities in a short regular review.
    Nexstella
    Keep dependencies and patches current, investigate issues and report what changed.

Run and improve

  1. Week 1

    You
    Share the improvements you have been waiting on and the reasons behind them.
    Nexstella
    Review the code and hosting, then turn your list into a backlog with the effort and risk of each item.

  2. Week 2

    You
    Choose the first improvements from the backlog and agree what done means.
    Nexstella
    Start the first improvement behind safe deployments, with tests around the parts we touch.

  3. Week 3

    You
    Try the change with a few users and tell us what works and what does not.
    Nexstella
    Release the change, watch how it behaves and keep the routine maintenance running alongside it.

  4. Each month

    You
    Set the next priorities in a planning review.
    Nexstella
    Report on maintenance, incidents and improvements, and keep the backlog up to date.

Hand over to your own hire

  1. Week 1

    You
    Tell us about your new developer and when they start.
    Nexstella
    Keep the product running and write down what a new developer needs to know.

  2. Week 2

    You
    Give your new developer time to work alongside us on real tasks.
    Nexstella
    Pair with them on deployments, fixes and the monitoring setup.

  3. Week 3

    You
    Let your developer lead the changes while we review.
    Nexstella
    Review their changes, answer questions and hand over every account and document.

Talk this through with us →

02 A typical situation

What this usually looks like

A business might come to us after its freelance developer took a full-time job, leaving a customer-facing application, a hosting account in someone's personal name and no notes on how to release a change.

We would agree the scope, access and escalation first, then take an inventory, move accounts into the business's name and make releases repeatable. Fixes would come next, then improvements in the order the business sets, with everything written down as we go.

Running cloud infrastructure? See BuiltForProd Managed

03 Start

Hand us the keys and keep the ownership

Book a call with an engineer. Tell us what the product does and what you know about how it was built, and we will explain what taking it over would involve.

What happens next

  1. You pick a time, or send us a message.
  2. A person at Nexstella reads what you shared before we talk.
  3. You leave with a clear next step, even when that step is to wait.

Or write to [email protected]. Send a brief instead

Meet

Pick a time with an engineer

What is your work email? The calendar invite and the video link go there.

The invite goes to the calendar you work from. Personal address? Use the Contact tab . If you stop before picking a time, we send one reminder to this address, and nothing else.

30 minutes, video call with an engineer · Times show in your time zone

What happens next

  1. You pick a time, or send us a message.
  2. A person at Nexstella reads what you shared before we talk.
  3. You leave with a clear next step, even when that step is to wait.

Contact

Send us a message

Pick the topic that fits and tell us what you are working on. A person replies within one business day.

A person replies from a real address.

Phone (optional)

Choose the country code, then type the number without it.

The topic leads the subject line, so the right person picks it up first.

A few sentences is plenty. You do not need to know which technology you need.

We use what you send to reply and, if it leads somewhere, to scope the work. Read the privacy notice, or write to [email protected].

Want the full picture? Read Ongoing engineering and platform support.

Also written for you: Reliability and observability , Prototype to production .

Last updated