top of page
.png){kind=small}
Get the AI-native proptech app you want, without the SaaS platform you don't.
The problem with most SaaS platforms: you pay for a whole suite and use a fraction of it, locked into terms far bigger than the job. Runway Hub is different. Each app is AI-native, built to do one specific proptech job, and priced to match what it delivers. Subscribe to what you need today. Add or remove as you grow.
Preview our first Apps
Why Runway Hub
Launch property apps. Earn ongoing revenue.
Runway Hub is open to anyone who can build. Runway staff. Clients with domain expertise. External developers who know property. Every Runway Hub app earns its creator ongoing revenue from every client who subscribes.
Built on enterprise infrastructure. Secure by default.
Every Runway Hub app runs on the Runway platform — a headless, AI-native data layer with documented APIs, bidirectional integration with your existing business systems, and security designed for enterprise procurement.
Two-factor authentication. Role-based access control. Single sign-on. Encrypted in transit and at rest. SOC-equivalent infrastructure. Your data stays yours.
Frequently asked questions
The platform's APIs are the product. The UI is one of many ways to access the platform — a Runway Hub app is another, an AI agent is another, an external integration is another. You can build whatever interface you want on top of the same data and workflows.
No. You can subscribe to a Runway Hub app, embed it in your own website, expose it through your own app, or access the data through APIs and AI agents. The platform doesn't require you to use any specific frontend.
The data stays in the platform's shared data layer. Other apps you use can still access it. If you stop using Runway entirely, you can export your data in standard formats.
Production environments are in Australia (Sydney) and the United States (Virginia). Customers can specify which region their data resides in. Cross-region data movement requires explicit consent.
Target uptime is 99.95% across both regions. Enterprise customers can negotiate specific SLA terms in their service agreement.
Platform updates ship weekly. Updates are backward-compatible by default. Breaking changes are flagged 60 days in advance with a documented migration path. App creators are notified directly; customers see no disruption.
Yes. Sandbox access is available for app creators and for enterprise customers evaluating the platform. The sandbox uses anonymised demo data (the Wonderland community) and is operationally separate from production.
Yes. The data layer is structured for AI agents to read, reason over, and act on. Agents authenticate using the same mechanisms as any other consumer (API keys, OAuth, service accounts) and operate within the same permissions model. You decide which agents have access to which data.
We operate with controls aligned to SOC 2 Type II, ISO 27001, GDPR, the Australian Privacy Principles, and CCPA. Formal certifications can be provided on request to enterprise customers under NDA.
Yes. The platform supports bidirectional integration with most major business systems used by builders and developers. Specific integrations are configured during onboarding based on your existing stack. Talk to us about what you use; we've integrated with a lot.
Yes. Email rowan@runway.com.au for an introduction. We'll connect you with whoever's most relevant — architecture, security, or integration — for your conversation.
Creators earn an ongoing share of net subscription revenue from every customer who uses their app, for as long as the app is on Runway Hub. The specific share is agreed when you register your idea and is documented in your creator agreement. It depends on the app, the effort involved, and whether you're a Runway staff member, a client, or an external developer.
Because no two apps are the same. A substantial app built by a small team deserves different terms from a focused app built by a single creator. Runway staff, clients, and external creators all earn on the same revenue share basis — we'd rather have a conversation about the right deal for your specific app than commit to a number that doesn't fit.
You retain rights to your underlying code. Runway has exclusive distribution rights for the life of the app on Runway Hub. You can't ship the same app to a competing marketplace while it's on Runway Hub. Specific IP terms are in the creator agreement.
You're expected to respond to critical bugs within five working days and ship fixes within 30 days. If the underlying Runway APIs change, we give you 60 days' notice to update. If you can't maintain an app, talk to us — we'd rather work it out than retire the app.
Yes, and it's encouraged for substantial apps. How you split your share with your partners is your agreement to make. Runway pays the registered creator; distribution within your team is your responsibility. Sort out the split upfront so there are no surprises later.
This is why we ask you to fill in the form before you start. If your idea overlaps with an app in development, we'll tell you within 48 hours and suggest either combining forces or finding an adjacent space. We've had this happen — two creators with the same idea — and it's better to know upfront than for both to ship and one to lose.
Most creators are developers, but not all. If you have deep domain knowledge but can't build, partner with someone who can. Many of the best apps come from a domain expert and a developer working together.
Familiarity with REST APIs, modern web development, and ideally AI development tools (Claude, Cursor, etc.). The Runway APIs are documented. The Creator Guide covers the architecture standards. If you've shipped a SaaS product before, you can ship a Runway Hub app.
Yes. Before your app goes live, it's reviewed against the architecture standards, the one-problem principle, and the existing app catalogue. The review checks API usage, security, design consistency, and avoids duplication. Most apps pass review with minor adjustments; the review is to help you ship, not to gatekeep.
If you can build property apps and you're already inside Runway, working with us as a client, or someone we know professionally — yes. We're building Runway Hub deliberately with a network of trusted creators, not opening a free-for-all. If you're not in one of those groups and you're keen, fill in the form anyway. We're always interested.
No. Configure the whole thing by chatting to the AI - tell it what you want and it builds it. Import your lots, style the map, deploy.
Explore the community, tap any lot for price and plans, ask the Map AI anything, and "fly" to key points of interest. It's a sales tool, not a static picture.
If you run Runway's CRM, yes - automatically. Own sales system? Keep it current in one action with the bulk status updater. Either way it's never stale.
Yes. Load your lots, keep the map current, deploy to your site. You don't switch CRMs to get a live masterplan.
Lot shapes: upload from Illustrator or GeoJSON, or draw them. Home specs and models: upload PDFs and let AI build the inventory, or connect an XML feed.
Both. Plans of subdivision and plats are first-class concepts, across both markets.
No. Bring your own data and publish. Run Land, Homes or CRM too and the map wires in automatically - but nothing else is required for a live map on your site.
The platform's APIs are the product. The UI is one of many ways to access the platform — a Runway Hub app is another, an AI agent is another, an external integration is another. You can build whatever interface you want on top of the same data and workflows.
No. You can subscribe to a Runway Hub app, embed it in your own website, expose it through your own app, or access the data through APIs and AI agents. The platform doesn't require you to use any specific frontend.
The data stays in the platform's shared data layer. Other apps you use can still access it. If you stop using Runway entirely, you can export your data in standard formats.
Production environments are in Australia (Sydney) and the United States (Virginia). Customers can specify which region their data resides in. Cross-region data movement requires explicit consent.
Target uptime is 99.95% across both regions. Enterprise customers can negotiate specific SLA terms in their service agreement.
Platform updates ship weekly. Updates are backward-compatible by default. Breaking changes are flagged 60 days in advance with a documented migration path. App creators are notified directly; customers see no disruption.
Yes. Sandbox access is available for app creators and for enterprise customers evaluating the platform. The sandbox uses anonymised demo data (the Wonderland community) and is operationally separate from production.
Yes. The data layer is structured for AI agents to read, reason over, and act on. Agents authenticate using the same mechanisms as any other consumer (API keys, OAuth, service accounts) and operate within the same permissions model. You decide which agents have access to which data.
We operate with controls aligned to SOC 2 Type II, ISO 27001, GDPR, the Australian Privacy Principles, and CCPA. Formal certifications can be provided on request to enterprise customers under NDA.
Yes. The platform supports bidirectional integration with most major business systems used by builders and developers. Specific integrations are configured during onboarding based on your existing stack. Talk to us about what you use; we've integrated with a lot.
Yes. Email rowan@runway.com.au for an introduction. We'll connect you with whoever's most relevant — architecture, security, or integration — for your conversation.
Buy an app
Browse the marketplace. Subscribe today. Cancel anytime.
Build an app
Earn ongoing revenue from every Runway customer.
Questions about one of our apps?
App Enquiry Form
Chat with a Runway Hub expert
bottom of page