SlideShare a Scribd company logo

The No Stack Startup

•
•
Albert Wenger
Albert Wenger

The document discusses how startup costs and infrastructure requirements have changed over time, from expensive dedicated servers and bandwidth in the 1990s to today's cloud services that allow building applications with minimal costs. It outlines how modern developers can compose applications by leveraging existing services through APIs for tasks like voice/video, storage, payments, forms, and more. This "no stack" approach allows focusing on the user experience rather than development, taking advantage of the scale and capabilities of underlying services.

Related slideshows

GrowthStack 2016 — 2017 Update to the Mobile Growth Stack
GrowthStack 2016 — 2017 Update to the Mobile Growth StackGrowthStack 2016 — 2017 Update to the Mobile Growth Stack
GrowthStack 2016 — 2017 Update to the Mobile Growth Stack
 
Lean Analytics for Intrapreneurs (Lean Startup Conf 2013)
Lean Analytics for Intrapreneurs (Lean Startup Conf 2013)Lean Analytics for Intrapreneurs (Lean Startup Conf 2013)
Lean Analytics for Intrapreneurs (Lean Startup Conf 2013)
 
Emerging Trends in Online Search
Emerging Trends in Online SearchEmerging Trends in Online Search
Emerging Trends in Online Search
 
1 of 16
Download to read offline
The No Stack Startup Video Hackday Presentation
 @albertwenger
The No Stack Startup
The 90s: Everything from Scratch
Once Upon a Time • Connectivity: dedicated bandwidth at $10,000 per month • Servers: $20,000 per box • Storage: $1,000/GB • Software licenses: $20,000+ to get started (Solaris, Oracle)
The early 00s: Dedicated Hosting
Oh So Modern • Connectivity: starting as low as $1,000/month • Servers: $1,000/month for minimal set up • Storage: $10/GB • Software: LAMP stack - free!
The late 00s, early 10s: Amazon Web Services
Cloudy • Connectivity: pay as you go, 10 cents/GB • Servers: pay as you go, 20 cents/hour • Storage: pay as you go, 12 cents/GB • Software: Ruby on Rails, Node.js, MongoDB
Now: No Stack
No Stack Create new experiences and solutions 
 by composing services with APIs
Service / API for Everything • Voice calls, text messages eg Twilio • Video recording and playback eg Ziggeo • Image and video classification eg Clarifai • Synchronization eg Firebase (Google) • Fraud detection eg Sift • Forms eg Typeform • File uploads eg Filepicker • Search eg Algolia • Feeds eg Stream.io
Examples • Applicant tracking: Typeform + Ziggeo • Mobile sales: Twilio + Stripe • Video speed dating: Tokbox + Firebase
Why? • Minimize development work, focus on user experience / business model innovation • Immediately support global reach • Pay as you go, often start with free tier • Benefit from scale economies and network effects of underlying services
Scriptable Integration • IFTTT • Zapier • More to come
1-person 1-week 
 1-million user startup
Have Fun! @albertwenger

More Related Content

The No Stack Startup

  • 1. The No Stack Startup Video Hackday Presentation
 @albertwenger
  • 4. Once Upon a Time • Connectivity: dedicated bandwidth at $10,000 per month • Servers: $20,000 per box • Storage: $1,000/GB • Software licenses: $20,000+ to get started (Solaris, Oracle)
  • 6. Oh So Modern • Connectivity: starting as low as $1,000/month • Servers: $1,000/month for minimal set up • Storage: $10/GB • Software: LAMP stack - free!
  • 7. The late 00s, early 10s: Amazon Web Services
  • 8. Cloudy • Connectivity: pay as you go, 10 cents/GB • Servers: pay as you go, 20 cents/hour • Storage: pay as you go, 12 cents/GB • Software: Ruby on Rails, Node.js, MongoDB
  • 10. No Stack Create new experiences and solutions 
 by composing services with APIs
  • 11. Service / API for Everything • Voice calls, text messages eg Twilio • Video recording and playback eg Ziggeo • Image and video classification eg Clarifai • Synchronization eg Firebase (Google) • Fraud detection eg Sift • Forms eg Typeform • File uploads eg Filepicker • Search eg Algolia • Feeds eg Stream.io
  • 12. Examples • Applicant tracking: Typeform + Ziggeo • Mobile sales: Twilio + Stripe • Video speed dating: Tokbox + Firebase
  • 13. Why? • Minimize development work, focus on user experience / business model innovation • Immediately support global reach • Pay as you go, often start with free tier • Benefit from scale economies and network effects of underlying services
  • 14. Scriptable Integration • IFTTT • Zapier • More to come