Keep the website healthy — and keep improving it.

Short answer: TUNDRÄ is a website maintenance and development subscription for teams with continuous work. It includes eligible implementation, QA, safe publishing and documentation. It is not a bundled hosting plan, a 24/7 monitoring service or a guarantee that every queued request finishes within the month.

What a website maintenance subscription should solve

A website rarely becomes “finished.” Campaign copy changes, integrations expire, plugins update, browsers change and real visitors find edge cases that a launch checklist missed. The maintenance model should make those requests easier to start without turning every fix into a new vendor search and proposal.

TUNDRÄ is designed for marketing, product, e-commerce and agency teams that already have a functioning website but lack a consistent owner for the backlog around it.

What can go into the monthly queue

What the subscription does not silently bundle

Many “maintenance plans” combine unrelated services. TUNDRÄ keeps the boundary explicit so the team does not imply controls it is not operating.

How ongoing website support works

1. Add a rough request. A URL, screenshot, voice note or description is enough. Credentials belong in the portal's write-only Secrets area or a least-privilege platform invitation.
2. TUNDRÄ triages the task. The team clarifies the outcome, identifies risk and splits large work into visible steps when needed.
3. The queue sets priority. Maintain works on one active task; Grow works on up to two. You can reprioritize ready work in the portal.
4. You review the right moments. Previews, risky changes and production approvals return as explicit decisions rather than recurring status calls.
5. The change is documented. Completed work includes the result, relevant checks, links and follow-up notes.

When a subscription is worth it

The model works when there is enough useful work to keep a queue moving and the tasks share project context. It is usually a fit when several of these are true:

• marketing regularly needs landing pages, copy changes or tracking fixes;
• the last developer or agency is no longer reliably available;
• small requests repeatedly stall because every change needs a fresh quote;
• the website spans CMS, frontend, backend and third-party integrations;
• the team wants changes delivered with QA and release notes, not loose code snippets;
• there is recurring work but not enough of one kind to justify another full-time hire.

When not to buy a maintenance subscription

If a stable brochure site needs one or two predictable edits a year, paying per task is likely more efficient. A dedicated hire can be better when daily internal collaboration and guaranteed capacity matter. A specialist managed host is better when the primary need is backups, malware monitoring, uptime and server operations rather than continuous development.

Current plans and limits

Maintain is $1,450/month for up to two projects, one active task and an initial response within four hours. Grow is $2,450/month for unlimited projects, up to ten team members, two active tasks and an initial response within two hours. Both include unlimited queued requests and can be cancelled for future renewal.

Completion time still depends on complexity, access, approvals and third-party systems. “Unlimited requests” is a queue rule, not a promise of unlimited simultaneous labour.

Website maintenance checklist for the first month

1. List the website, repository, hosting, domain and integration owners.
2. Confirm a backup or recovery point before material production changes.
3. Record current build, lint and test commands.
4. Prioritize revenue and lead paths: checkout, forms, account access and analytics.
5. Update high-risk dependencies in small batches with rollback notes.
6. Check responsive layouts and accessibility on the highest-traffic templates.
7. Document every shipped change and the next observable follow-up.

Frequently asked questions