Plan Project

Managed hosting and services for your online platform.

Altha Technology runs your online presence — public websites, private Nextcloud workspaces, custom integrations, creative support, and the planning to keep it maintainable.

See our work Plan Project
We Run Apps and infrastructure we own and operate — your site, your workspace, your tools, never at a vendor’s mercy. We Build Custom code, content, AI-assisted dev, and video — built by the people who answer your questions. We Maintain Updates, backups, monitoring, and security — without you having to think about it.
01 / RUN

We Run

Your sites, your team's workspace, your mailbox — running on hardware we own and operate ourselves. Open-source apps configured for the way you actually use them, so the work, the data, and the way out always belong to you.

  • Private servers we own and operate in our own facility — your traffic runs on hardware with an address we can point to
  • Your WordPress or WooCommerce store on a per-customer slot — nginx / PHP-FPM / MariaDB tuned for your traffic, never sharing CPU or memory with strangers' workloads
  • Your team's files, calendar, contacts, chat, and project boards in a private Nextcloud — server-side encrypted, you control who sees what
  • Other open-source apps we run: GitLab (private git + CI), Invoice Ninja (invoicing), Mastodon (social), poste.io (mail)
  • Edge TLS and ACME handled by us; per-customer microVMs isolated on their own addresses
  • Mail delivery wired correctly — SPF, DKIM, DMARC, reverse DNS — so your emails actually land in inboxes, not spam folders
02 / BUILD

We Build

Custom code, custom content, and the integrations between them. When the stock setup doesn't fit, we build the missing piece — and when the raw material you've shot or written needs to become something that ships, we play the supporting role.

  • Custom WordPress: themes, mu-plugins, REST endpoints, Gutenberg blocks — no page-builder lock-in
  • Migration off page builders (Divi, Elementor) and closed platforms (Wix, Squarespace) onto maintainable custom code
  • Your integrations and automation pipelines — REST endpoints, webhooks, CRM connectors that quietly do the work between systems
  • AI-assisted code review, refactoring, and pair-programming on your project — we use the same agent tooling on our own fleet, and this site was rebuilt that way with the work documented as it happened
  • Your raw footage → reels, shorts, clips, and long-form video — you bring the story, we handle the timeline
  • Your page structure, content polish, and technical writing — shaped from what you bring into something visitors can act on
03 / MAINTAIN

We Maintain

Launching a site is the easy part. Keeping it online — updated, backed up, monitored, defended, and recoverable — is the work “managed” actually means. We pay attention to it so you don't have to.

  • Your site stays current — OS and application updates applied with safe rollback; WordPress core and plugin updates tested before they hit your live site
  • Your backups actually restore — off-site, verified, with TrueNAS snapshots and scheduled exports you can take with you whenever
  • Vulnerability monitoring — Wordfence on WP, package CVE tracking at the OS layer
  • Security audits and reviews on your code or our deployments
  • Exit paths: documented exports, open protocols, recoverable formats — leaving us is always cheaper than staying out of obligation
  • Incident logs shared with the customer when things break; no black-box postmortems
altha@fleet:~ — services 149 services up
NAME KIND COUNT NOTE
wordpresscms86customer sites + agency-managed clients
nginxhttp12static sites + custom origins
peertubevideo8federated video hosting
nextcloudgroupware4files · calendar · contacts
avideovideo4video platform
invoice-ninjabilling3self-hosted invoicing
dnsdns1authoritative for althadns.com
misc / custommixed31matrix · mastodon · nostr · mail · btcpay · vaultwarden · bitwarden · jellyfin · castopod · wiki.js · zammad · restreamer · games · gitlab · edge proxies

Own the data. Protect the data. Serve the data.

As more of life moves into digital systems, the people who use them should keep authority over the tools, the data, and the choices that shape them.

We hold these truths to be self-evident: every person owns their digital existence, privacy is a natural right and not a permission, devices and software belong to the people who acquired them, and technology must expand human autonomy rather than narrow it.

Altha Technology builds durable, owner-controlled systems for the people and organizations who share that conviction.

01

Ownership

Devices, software, and data, once lawfully obtained, belong to the people who use them — to run, modify, repair, and migrate.

02

Privacy

How personal data is collected, stored, shared, or deleted is the owner’s call — not a platform’s, not a watcher’s, not by default.

03

Self-determination

The freedom to leave, to migrate, to retract presence from systems no longer consented to — without losing the work itself.

Independence runs on open source.

Open source means the right to inspect, modify, run, and migrate the tools your work depends on. Closed platforms can change terms, raise prices, or shut the door at will — open ones can be forked, audited, and kept running by anyone who chooses to. We build on open-source pieces so the work, the data, and the exit always belong to you.

01

Direct contact paths

Route visitors to your site, your form, and your email list — channels you own.

02

Exit paths

Exports, open protocols, backups, and clear recovery options — so nothing locks you in.

03

Maintained systems

Updates, documented integrations, verified backups, and actively operated infrastructure.

Recent writing on websites, cloud tools, and ownership.

These articles give context for the problems Altha Technology works on: data ownership, platform dependence, web basics, and practical migration decisions.

View all writing →

Talk through your online presence.

Tell us what you host today, what tools your organization depends on, and what needs to be easier to maintain. We can start with hosting, private cloud, development work, creative work, or a migration path.

Project context Start with the shape of the project.

The form is meant to sort the conversation, not force a finished scope. Plain notes are enough.

  • A current website or workspace
  • A problem that keeps coming up
  • A system you want easier to maintain
Contact details Contact details identify the working context.

Use the organization, project name, or domain that best fits the work.

  • An existing site or domain
  • A business or team name
  • The best email for follow-up
Service area Pick the closest lane.

The choice helps route the first reply. Mixed projects are normal.

  • Hosting for public websites and forms
  • Private cloud for files and calendars
  • Dev or creative work around the system
Service area Hosting / public web presence

Choose this when the public website, landing pages, forms, or email delivery are the main concern. The first reply can sort whether this is maintenance, migration, cleanup, or a new launch.

Helpful details include the current domain, where the site is hosted, what forms or mailboxes are involved, and what needs to keep working during the move.

Service area Private cloud / team workspace

Choose this when files, calendars, contacts, sharing, or team access are the practical problem. This usually means Nextcloud planning, migration, permissions, and ongoing support.

Helpful details include where files live now, who needs access, what calendars or contacts matter, and whether a closed suite needs to be replaced gradually.

Service area Dev work / integrations

Choose this when the site or workspace needs custom behavior: WordPress customization, plugin cleanup, automations, internal tools, CRM flow, or data moving between systems.

Helpful details include the tool names, the current manual steps, what should happen automatically, and where the workflow breaks today.

Service area Creative work / content and design

Choose this when the problem is clarity: messaging, page structure, visuals, content, campaign pages, or helping people understand what you do before the technical work begins.

Helpful details include pages that feel unclear, examples you like, assets you already have, and the audience the work needs to reach.

Service area Moving away from another platform

Choose this when the main goal is reducing dependence on an account, suite, marketplace, or hosted platform. The first plan usually separates what must move now from what can move later.

Helpful details include the platform, renewal dates, export options, user accounts, files, forms, email, and anything that cannot go offline during the transition.

Service area Not sure yet

Choose this when the project does not fit one lane yet. That is normal when the work touches hosting, files, content, email, and internal processes at the same time.

Start with the pain point, the tools involved, and what would make the system easier to own or maintain.

Current setup Describe what exists today.

List the tools, accounts, hosting, or manual steps that are already in place.

  • WordPress, Wix, Squarespace, or shared hosting
  • Google Drive, Microsoft 365, Dropbox, or email
  • Forms, CRM, calendars, files, or manual handoffs
Project goal Say what needs to change.

This can be a technical fix, a clarity problem, or a workflow that needs to stop being fragile.

  • Move files out of a closed platform
  • Make forms and email delivery reliable
  • Refresh page structure, content, or integrations
Timeline Timeline sets the first plan.

A deadline changes the path. A planning window gives more room for cleanup and migration.

  • A launch date or campaign deadline
  • A renewal or platform cutoff
  • A slower rebuild with fewer surprises
Timeline This month

Use this when there is an active deadline, launch, renewal, or event. The first step is deciding what must work now and what can wait until the pressure is lower.

Include the date, the risk if it slips, and whether the existing site, files, forms, or email have to stay online during the work.

Timeline 1-3 months

This window works well for a focused build, cleanup, migration, or phased launch. There is usually enough time to review the current setup before moving pieces.

Helpful details include desired launch timing, review cycles, access needs, and which parts of the system are most important.

Timeline Planning ahead

Use this when the goal is to make a better decision before committing to a full move or rebuild. The first reply can focus on options, order of operations, and risks.

This is a good fit for platform exits, future website work, private cloud planning, or replacing a workflow in stages.

Timeline Urgent

Use this when something is broken, exposed, close to renewal, or blocking normal work. The first plan usually separates stabilization from the larger cleanup.

Include what changed, who is affected, any error messages, and the fastest safe way to reach you.

Budget range Budget gives the project a frame.

A rough range helps separate quick fixes, phased work, and full rebuilds.

  • A small repair or migration
  • A focused site or cloud setup
  • A larger technical and creative project
Budget range Under $1,000

This usually fits a narrow repair, consultation, small migration, audit, content adjustment, or a clear one-part fix.

Helpful details are the single most important outcome and what would make the project successful without expanding the scope.

Budget range $1,000-$3,000

This can cover focused implementation: hosting cleanup, a small site or form flow, a private cloud starting point, a migration path, or a specific integration.

Useful notes include what already exists, what should be kept, and which pieces need to work together first.

Budget range $3,000-$7,000

This range gives room for a more complete site, workspace, migration, or technical and creative project with planning, implementation, testing, and handoff.

Helpful details include content status, integrations, users, migration size, and any launch or approval schedule.

Budget range $7,000 or more

This usually means a larger rebuild, multi-system migration, custom workflow, private cloud rollout, or ongoing support plan.

Start with the business problem, the systems involved, and the outcome that would justify the investment.

Budget range Not sure yet

This is fine when the scope is still forming. The first reply can outline likely paths, what affects cost, and where a phased start would make sense.

Useful notes are the problem, the deadline, and whether this is exploratory, urgent, or already approved.

Best next step Choose the easiest next step.

The first reply can be questions, options, or a scheduled call depending on how ready the project is.

  • Email first if the scope is rough
  • Schedule a call if timing matters
  • Ask for options if you are comparing paths
Best next step Email me first

Choose this when you want a written first pass. The reply can ask clarifying questions, identify missing details, or suggest a practical next step.

This works well when the project is early, when several people need to review, or when you want to share links and notes first.

Best next step Schedule a call

Choose this when timing, priorities, or several moving parts need to be talked through. A call is useful when the first decision depends on context.

Include any time constraints, who should be involved, and what you want to decide during the call.

Best next step Send options or questions

Choose this when you are comparing paths and want a practical read on what is possible. The reply can frame tradeoffs before a call or proposal.

This is a good fit for unsure budgets, platform exits, or projects that could start in more than one place.

Additional context Add anything that changes the picture.

Useful context is often the detail that does not fit a radio button.

  • Current pain points or failed attempts
  • People, approvals, or access constraints
  • Links, examples, or must-keep requirements
Homepage Project Intake