MKUltraman / Operating system

Ultra
Stack.

67 tools, each with a defined job. One management layer that keeps them from becoming 67 separate problems.

How FrontierStack manages it ↓

The management layer

FrontierStack

FrontierStack is how I manage the Ultra Stack as a working system. It defines what each tool is for, what information belongs there, how work moves between tools, who owns the result and how the work can be recovered or moved later.

The goal is not to collect software. It is to give every recurring job a dependable path from intake to decision to finished output. If two tools do the same job without a reason, one should leave. If a tool holds important data, its access, backup and exit path need to be explicit.

  1. Assign the job.Every tool has a defined role and boundary.
  2. Control the handoff.Information moves through named interfaces, not copy-and-paste folklore.
  3. Keep proof.Sources, tests, approvals and finished artifacts stay attached to the work.
  4. Preserve an exit.Important data remains exportable, recoverable and owned.
01

Stack category

AI

OpenAI OpenAI General reasoning, coding, research synthesis and multimodal production. Why I use it → Anthropic Anthropic Long-context analysis, careful drafting and codebase work. Why I use it → Google Google Search, Workspace, analytics, maps and an additional AI perspective. Why I use it → Hermes Nous Research The agent workspace that joins conversation, tools, files, research and execution. Why I use it → Ollama Ollama Local model execution for private, offline or experimental work. Why I use it → Perplexity Perplexity Fast web reconnaissance with visible source links. Why I use it → VibeProxy Automaze Local routing from AI coding tools to authenticated model providers. Why I use it → Mistral Mistral AI · Contextual European frontier and open-weight models for reasoning, coding and controlled deployments. Why I use it → Groq Groq · Contextual Very fast hosted inference for supported open models. Why I use it → OpenRouter OpenRouter · Contextual One API and routing layer across many hosted AI models. Why I use it →
02

Stack category

Analysis

Screaming Frog Screaming Frog Technical crawling and site-wide SEO inspection. Why I use it → Ahrefs Ahrefs · Contextual Search research, backlink inspection, competitor discovery and content opportunity analysis. Why I use it → Similarweb Similarweb · Contextual Market and competitor traffic estimates for directional digital research. Why I use it → Google Analytics Google · Preferred First-party website measurement for acquisition, behavior and conversion paths. Why I use it →
03

Stack category

Infrastructure

Docker Docker Repeatable local environments and portable service packaging. Why I use it → Supabase Supabase Postgres databases, authentication, storage and application backends. Why I use it → Apple Apple The hardware, operating system and creative foundation of the stack. Why I use it →
04

Stack category

Web design

I steer most new work toward WordPress, Squarespace or Sanity with Astro, depending on the publishing model and the team that will own it. Webflow remains useful in the right design-led context. Wix, Drupal and Weebly are primarily migration work.

Preferred

WordPress WordPress project · Preferred Flexible publishing and content-heavy websites with broad ownership options. Why I use it → Squarespace Squarespace · Preferred Managed websites for organizations that value simplicity over deep customization. Why I use it → Sanity Sanity · Preferred Structured content infrastructure for custom websites and multiple publication channels. Why I use it → Astro Astro Technology Company · Preferred A content-focused web framework for fast, maintainable custom sites. Why I use it →

Contextual

Webflow Webflow · Contextual Visual production of custom marketing sites with managed hosting. Why I use it →

Migration only

Wix Wix · Migration only A managed site builder I support mainly during assessment and migration. Why I use it → Drupal Drupal Association · Migration only A capable open-source CMS I usually encounter in complex legacy estates. Why I use it → Weebly Block · Migration only A legacy managed builder I support primarily to recover and migrate sites. Why I use it →
05

Stack category

Commerce

Stripe Stripe Online payments, checkout and programmable billing. Why I use it → PayPal PayPal A familiar alternative payment and invoicing channel. Why I use it →
06

Stack category

Hosting and domains

Cloudflare, Porkbun and Kinsta are preferred destinations for different needs. Vercel, DigitalOcean, Hostinger, Namecheap and WPMU DEV remain useful where they fit. GoDaddy is primarily an estate I help clients leave safely.

Preferred

Cloudflare Cloudflare · Preferred DNS, edge security, caching and selected hosting services. Why I use it → Porkbun Porkbun · Preferred Straightforward domain registration with transparent day-to-day controls. Why I use it → Kinsta Kinsta · Preferred Managed WordPress hosting for sites where performance and operational support matter. Why I use it →

Contextual

Vercel Vercel Git-connected deployment, previews and hosting for modern web projects. Why I use it → Hostinger Hostinger · Contextual Budget-conscious managed hosting for conventional websites. Why I use it → Namecheap Namecheap · Contextual Domain registration and selected commodity web services. Why I use it → DigitalOcean DigitalOcean · Contextual Cloud servers and managed infrastructure with a relatively direct operating model. Why I use it → WPMU DEV WPMU DEV · Contextual WordPress hosting, management and maintenance tools for multiple sites. Why I use it →

Migration only

GoDaddy GoDaddy · Migration only A registrar and hosting estate I usually work to simplify or leave. Why I use it →
07

Stack category

Source control

GitHub GitHub · Preferred Canonical Git repositories, review, automation and release coordination. Why I use it → GitLab GitLab · Contextual Integrated Git hosting and delivery workflows for teams already invested in GitLab. Why I use it →
08

Stack category

Communication

Signal and email are my preferred channels for efficient, private direct communication. WhatsApp, Facebook Messenger, LINE, Slack and Discord are bridge channels used to begin a conversation where people already are. The goal is to move sustained work toward Signal and email. Bitchat and Bridgefy provide separate mesh-network options for resilient local communication.

Preferred channels

Spark Readdle · Preferred Focused email across multiple accounts. Why I use it → Signal Signal Messenger · Preferred Private real-time messaging and calls. Why I use it →

Contextual

Matrix The Matrix.org Foundation · Contextual An open protocol for federated and self-hostable real-time communication. Why I use it →

Bridge channels

WhatsApp Meta · Bridge A widely adopted bridge channel for contacts who already use it. Why I use it → Facebook Messenger Meta · Bridge A bridge channel for contacts and communities organized on Facebook. Why I use it → LINE LY Corporation · Bridge A necessary bridge channel for everyday communication in Japan. Why I use it → Slack Salesforce · Bridge A bridge into organizations whose teams already work in Slack. Why I use it → Discord Discord · Bridge A bridge channel for online communities, creative groups and technical projects. Why I use it →

Resilient mesh

Bitchat Permissionless Tech · Resilient mesh Bluetooth mesh and Nostr messaging for communication beyond normal centralized channels. Why I use it → Bridgefy Bridgefy · Resilient mesh Bluetooth-based offline messaging and mesh-network technology. Why I use it →
09

Stack category

Publishing

Publishing deserves its own category. Mailchimp and Substack manage one-to-many audience relationships, subscriber consent, editorial cadence and public archives. They are not substitutes for direct communication.

Mailchimp Intuit Mailchimp · Contextual Managed mailing lists, campaigns, forms and audience automation. Why I use it → Substack Substack · Preferred Direct publication to a web archive and an opted-in email audience. Why I use it →
10

Stack category

Events

Luma Luma · Preferred Event pages, registration, invitations and guest communication. Why I use it →
11

Stack category

Knowledge

Obsidian Obsidian Local-first notes, durable Markdown and connected project knowledge. Why I use it → Notion Notion Shared operating pages, lightweight databases and client-visible coordination. Why I use it →
12

Stack category

Media

Final Cut Pro Apple Primary video editing and delivery on the Mac. Why I use it → HandBrake HandBrake Project Reliable video transcoding and delivery compression. Why I use it → GIMP GIMP Project Open-source raster image editing and practical asset repair. Why I use it → Logic Pro Apple Music production, recording, sound design and final audio work. Why I use it → PhotoScape MOOII Tech Fast batches, contact sheets, crops and routine image preparation. Why I use it → Canva Canva · Contextual Fast collaborative layouts, social assets, presentations and lightweight brand templates. Why I use it → DJI DJI · Preferred Cameras, stabilization and aerial imaging for location and production work. Why I use it → OBS Studio OBS Project · Preferred Open-source recording and live-production software for video, audio and screen capture. Why I use it → YouTube Google · Preferred Video publishing, discoverability, embeds and durable audience access. Why I use it →
13

Stack category

Security

Proton Proton Privacy-focused mail, calendar, storage and account services. Why I use it → WireGuard WireGuard project Simple, modern encrypted networking between trusted endpoints. Why I use it → Tailscale Tailscale Managed private networking between people, devices and services using WireGuard. Why I use it →
14

Stack category

Mac utilities

CleanMyMac MacPaw Storage inspection, application cleanup and routine Mac maintenance. Why I use it → Amphetamine William Gustafson Keeping the Mac awake during long, interrupt-sensitive jobs. Why I use it →

Tools are not the service

Let the Ultra Stack support your work.

I choose and manage tools in service of a real operating result. If your systems have become an accidental pile of subscriptions, I can help make the responsibilities, handoffs and risks clear.

Discuss your project →