Skip to main content

How Storify implementations roll out

Most implementations start with a focused rollout plan: confirm the desired operating model, align on data and access-control dependencies, then expand into br…

Written by Harman Sandhu
Updated this week

How Storify implementations roll out

Most implementations start with a focused rollout plan: confirm the desired operating model, align on data and access-control dependencies, then expand into broader automation and pricing workflows.

What this article covers

  • Typical implementation windows and what affects them

  • How teams run in parallel during transition

  • How rollout choices change when gate migration is involved

Implementation timing and support

  • General Platform: Q: How long does implementation take? Simple access control: 1 week.

  • Technical Reference: Component Requirement ----------- ------------- Browser Chrome, Safari, Firefox, Edge (latest versions) Mobile iOS 14+, Android 10+ (responsive web) Kiosk Any touchscreen device with web browser Network Standard internet connection Standard Description ---------- ------------- PCI-DSS Stripe handles all payment data SOC 2 Infrastructure compliance certified GDPR Data processing compliant ID Verification Stripe Identity for KYC Encryption TLS 1.3 in transit, AES-256 at rest Component Provider ----------- ---------- Payments Stripe (Connect for multi-tenant) Voice AI VAPI SMS Twilio Email Resend/SendGrid ID Verification Stripe Identity Access Control Kisi, HID, Brivo, etc. Metric Value -------- ------- Uptime SLA 99.9% Support Response 24-hour email, phone on higher tiers Maintenance Windows Sunday 2-4 AM (announced in advance) Failover Multi-region redundancy ---

Migration planning inputs

  • Migration Paths: Requires Storable's cooperation. Step Action Time Who ------ -------- ------ ----- 1 Extract all data from SiteLink (browser agent or API) 30-60 min Storify 2 Storable deletes Cloud Node from their Customer Account 5 min Storable 3 Storify creates new Customer Account in their PDK dealer portal 5 min Storify 4 Storify registers Cloud Node using serial number 5 min Storify 5 Cloud Node auto-connects under new account 2-5 min Automatic 6 Controllers auto-discover 5-10 min Automatic 7 Storify pushes all tenant codes via PDK API (from extracted data) 15-30 min Storify 8 Configure access rules, schedules, groups 30-60 min Storify 9 Test all gates 15-30 min Storify Data lost: All event history from old account.

Migration planning inputs (2)

  • Data Extraction: Data Priority Source Method ------ ---------- -------- -------- Tenant-to-code mappings Critical SiteLink/StorEdge Browser agent or SiteLink API (NDA) Gate group definitions (names, hours, days) High SiteLink Setup > Gate Browser agent Gate group keypad assignments High SiteLink Setup > Gate > Gate Groups Browser agent Gate group unit/customer mappings High SiteLink Gate Groups detail pages Browser agent Non-tenant codes (managers, fire dept) High SiteLink tenant records (accounts without rentals) Browser agent Activity/event history Low PDK Cloud Node / Storable backend Not extractable -- accept the loss The SiteLink API (DEI -- Data Exchange Interface) is NOT publicly documented. Access process: Email apisupport@sitelink.com Sign NDA Receive password-protected PDF documentation Set up Corp User account with API rights Pay monthly API fee Obtain API key Architecture: SOAP protocol.

Migration planning inputs (3)

  • Pre-Migration Data Extraction: This is where Storify's existing browser automation architecture (Browser Use) becomes a competitive weapon:

Next steps

  • Use this article during discovery and scoping calls.

  • Move next into the gate migration guides if physical access control is in scope.

References

Did this answer your question?