M MarBoba
Features

Everything between new project and green deploy, automated.

MarBoba is an opinionated internal developer platform. The opinions are shaped by shipping real products — what you see below is what small teams actually need, in the order they need it.

Master Project Wizard

Eleven steps, sensible defaults on every one, 10 minutes to a deploying dev branch. Pick a template, confirm the components, choose where each component deploys, and MarBoba pushes the real pipeline YAML to your repo. Every answer is changeable later; this is a shortcut, not a cage.

  • Auto-slugs your repo name from the project name
  • Pre-fills credentials that are already in your Vault
  • Shows a ✓ on deployment targets with ready-made templates for your VCS
  • Creates Dev / QA / Staging / Prod environments in one click

CI/CD pipelines, 108 templates

For every realistic combination of component × deployment target × VCS provider, MarBoba ships a production-grade YAML scaffold. Tests run first, builds are cached, prod deploys are gated behind a manual approval, and every run pings a callback URL so MarBoba records the run against the project.

  • Backend APIs to Cloud Run, Lambda, ECS, Heroku, Kubernetes, Fly.io, Render, Azure App Service
  • Web frontends to Firebase Hosting, Vercel, Netlify, Cloudflare Pages, GitHub Pages, S3+CloudFront
  • Mobile apps to Play Store (with Flutter / React Native / native) and App Store via TestFlight
  • Libraries to npm, PyPI, Maven Central, NuGet, crates.io, RubyGems
  • Desktop apps to GitHub Releases (cross-platform .dmg / .AppImage / .exe)

Multi-VCS from day one

GitHub, GitLab, Bitbucket, and Azure DevOps are all equal citizens. The CI/CD Runs page, the cancel button, the re-run button, the log viewer — they all dispatch through a single driver that talks to whichever provider your project uses. No forked code paths, no feature gaps.

  • List pipeline runs uniformly across all 4 providers
  • Cancel + rerun failed jobs for any provider
  • Push CI/CD config files to the right path for each provider automatically
  • Env Sync writes secrets to each provider's native CI variable store

Feature Flags

A real flag service built into the platform — no LaunchDarkly bill. Flags have per-environment overrides, targeting rules, kill switches, and a ready-to-paste client SDK shown in 13 languages. Already on LaunchDarkly? Import your whole project in one click.

  • Boolean / string / number / JSON flags with typed reads
  • Environment overrides (dev / qa / staging / prod) per flag
  • Percentage rollout, user segment, property-match, schedule rules
  • "How to Implement" panel ships code in TS/JS/Python/Dart/Swift/Kotlin/Java/Go/Ruby/PHP/C#/Rust/cURL
  • LaunchDarkly import pulls keys, types, defaults, environment overrides, and tags
  • Soft-stop on subscription lapse: flag reads keep returning defaults, no feature breakage

Vault & Env Sync

MarBoba's Vault stores every secret your pipeline needs — keystores, certificates, API keys, service-account JSON. Env Sync mirrors them into your VCS's native CI variable store (GitHub Secrets / GitLab CI Variables / Bitbucket Pipeline Variables / Azure Variable Groups) so pipelines can read them at runtime. Rotate in the Vault, it propagates in seconds.

  • KMS envelope encryption on every secret
  • Automatic sync mode triggers on every Vault write
  • Manual mode with a Sync button for regulated environments
  • Pipeline-failure log scanner points at the specific missing secret

Release Readiness

Each project tells you exactly what's blocking a release. Missing a Play Store service account? It's on the Environments tab with a Set Up button that takes you to the Credentials screen with the right keyword pre-filled. No guessing, no chasing Slack threads for the JSON key.

  • Per-platform progress (Android / iOS / Web)
  • Missing-credential list with one-click fix
  • Works for every platform — mobile, web, backend, library

See it in your browser.

The fastest way to know if MarBoba fits is to run the wizard on one of your own projects. Takes 10 minutes, leaves a real working pipeline behind.