A release pipeline that tests every update before it goes live
We set up hosting, databases, and a release pipeline for your app, in accounts you own where possible. Each update then runs its tests and a trial build before it ships.
Where your app runs and how each update gets out
Cloud setup decides where your app runs, how each update reaches your users, and how your team hears when something breaks. We set all of it up once, so every update after that goes out the same tested way.
Hosting and databases go in accounts you own where possible. Your team gets a written runbook for releasing, rolling back, and managing access, so your releases do not wait on us.
Here is how Ohana Events, an app we built, ships. The API tests and the app’s unit tests run on every proposed change, along with a security audit of its dependencies and a test build of the web app. Railway, which hosts the API and the web app, skips any release whose checks failed.
- Who it’s for
- Updates go out by hand, and each release depends on someone remembering every step.
- You are launching an app and want hosting and releases in place before the first users arrive.
- Your app runs in accounts that belong to a former developer or agency, and you want it moved into accounts you own.
- You hear about errors from your customers before your team sees them.
A tested way to ship, in accounts you own where possible
- A review of how your app is hosted and released today
- A build and release pipeline that runs tests and a trial build before anything ships
- Hosting and databases set up in accounts you own where possible
- Error reports and regular checks on the live app
- A written runbook covering how to release, how to roll back, and who has access
What happens between the review and the runbook
Scope
We ask how your app is hosted and released today and write down what we will review, move, and set up. You approve the scope and its price before we change anything.
Review what you have
We look at where it runs, who has access, and how an update gets out.
Set up hosting
We set up hosting and databases in accounts you own where possible, and move the app across if it needs to move.
Build the pipeline
We automate the route from code to your users. A change that fails its tests or its trial build stops there, before it reaches the live app.
Set up error reports
We add error reports and regular checks on the live app, so problems are flagged early.
Hand over the runbook
You get a written runbook covering how to release, how to roll back, and who has access. From then on, your team releases every update the same way.
How to start and what it costs
Start with a free call about what you want to build. We then write a scope and a price, and you approve them before any build work starts.
Cloud Solutions: From $5,000. Typically 2 to 4 weeks, for a release pipeline and hosting on one app.
Your data and what you own
- Where is our data stored?
- In your own accounts and tools where possible, otherwise in cloud services we set up for your project and name for you before work starts.
- What happens to our data when the work ends?
- We hand over or delete what we hold, as you choose, and remove our access to your systems.
- Who owns the code you write for us?
- You own what we write for you; we keep our own pre‑existing components. What you own at the end, such as code, accounts, and content, is agreed in writing for each engagement before work starts.
See it in practice
Ohana Events
Read the case study on Ohana EventsAn independent guide to the unofficial events around Salesforce conferences, with RSVPs, host‑approved guest lists, and QR check‑in at the door. One codebase runs the live web app and builds the iOS and Android apps.
- Includes
- Event guide and map; RSVPs and approval lists; QR door check‑in; Web, iOS, and Android from one codebase
- Tools on this build
- GitHub Actions, Railway, MongoDB, Sentry, pytest, Jest, Playwright
Questions about Cloud Solutions
Who owns the hosting accounts?
You own them where possible: Stratyx Ventures sets up hosting and databases in your own accounts, so they stay yours after we hand over. The runbook records who has access to each one.
Can you work with the hosting we have now?
Stratyx Ventures can keep what already works in your hosting. We start by reviewing how your app is hosted and released today, and the scope you approve says what stays and what changes.
What happens if a release goes wrong?
With the pipeline Stratyx Ventures sets up, a release goes live only after its tests and a trial build pass. If a problem still gets through, the written runbook shows your team how to roll back.
What do the regular checks on the live app do?
The regular checks Stratyx Ventures sets up test the live app on a schedule and flag what fails. On Ohana Events, a nightly run repeats the integration tests, runs the browser tests, and checks that the live site responds and is running the latest code.
Show us how your app ships today
We start with where it runs, who has access, and how an update gets out.