Beyond Saas: Building for Enterprise
summary
Travis CI adds an on‑prem Enterprise offering for customers behind firewalls, built from the same codebase rather than a fork, sold with site licenses checked in a license.yaml and paid via Stripe; the small team (≈7 growing to 23) tries a single mega container then pivots to Replicated for installs, automatic upgrades, metrics and backups, and ships a support bundle for debugging; long‑lived branches and merge pain slow development, pricing and contracts take 2–6 months, and buying installation tooling wins time over building it.
AI-written summary · about
chapters (7)
- 0:00Introduction and welcome
- 4:47Why enterprise matters
- 12:51Starting enterprise development
- 18:33Challenges of enterprise builds
- 22:30Lessons learned from enterprise
- 29:53Focus on your core product
- 31:38Key takeaways and conclusion
related talks
31mSaaS release engineering: balancing speed, safety & scale
35mScaling an Open Source CI with a Remote Team, the Story behind Travis CI
33mFrom SaaS to On-Premise - A DevOps Journey
46mThe Software Factory
06mSwitching to On-Premise - The When and the Why
28mScale CI/CD in Your Enterprise Through An Internal Spinnaker as-a-Service Model
01h 02mThe New Realities of SaaS: Why Building is Harder Than Ever
25mScaling Up, Not Out: Managing Enterprise Demands in a Growing SaaS Startup
