trustgrid Logo
  • Products
    • Connect
    • EdgeCompute
    • Remote Access
  • Solutions
    • Build Cloud-to-Edge Architectures with Docker Containers
    • Connecting SaaS Applications to Customer Data
    • Connect Cloud Services to On-Premise Systems
    • Remotely Manage On-Premises Applications
    • Connecting Distributed Applications
    • Trustgrid for AWS Transit Gateway
    • Trustgrid for OEM Integrations
    • Remote Access for Banking
    • Health Tech Connectivity
    • Trustgrid for WireGuard
    • Secure Remote Access
    • FinTech Connectivity
    • SASE
  • Resources
    • Core Integration Library
    • Blog
    • Content Library
    • Case Studies
    • Videos
    • Glossary
    • FAQ
  • Pricing
  • About Us
    • News
    • Partners
  • Contact
  • Support
  • Request Free Trial

"*" indicates required fields

Hidden

Reference Documents

Introduction to the Trustgrid Deployment

Frequently Asked Questions

Customer Deployment Diagram for Two Nodes with One IP Interface

Customer Deployment Diagram for Two Nodes with Two IP Interfaces

Deployment Instructions for Two Nodes with One IP Interface

Deployment Instructions for Two Nodes with Two IP Interfaces

If you have questions or need help filling out the form please contact Trustgrid at provisioning@trustgrid.io

i.e. Main Datacenter, Ops Center, DR Site, Boston, etc.
Device Type*
Hypervisor

Deployment Type*
Are rack mount devices required?
Interfaces on Each Device*

DNS

DNS servers can be public or private but must be accessible from the 1st interface of the node.

Device Network Information

IP Interface #1


IP Interface #2


First Device

IP Interface #1


IP Interface #2

Second Device

IP Interface #1 – 2nd Device


IP Interface #2 – 2nd Device

This will use the same subnet information from Interface #2 on the first device.

Cluster IP Address

The Cluster IP must be on the same network as the IP Interface #2 interface of each device, when two interfaces are used.

Host Information

IP address
i.e. Core Banking:12000-12020, e-statements:443, etc.
Test hosts (with descriptions) or any other info can be entered here.

On Connectivity Failure

In the event of a connectivity failure at the primary data center, how should Alkami fail over to your secondary data center?
Automated Failover / Automated Fail Back
This setting will provide the same Automated Failover as described above, but fail back will happen automatically as soon as connectivity is restored.

NOTE: Automated failover requires the ability for servers at the DR site to accept connections automatically and without manual approval

Manual Failover
This setting requires your IT team to contact the Mahalo Network team to manually failover between your data centers.

Deployment Address

This is the physical address where the Trustgrid node (s) will be deployed.
Address*

Technical Contact Information

Trustgrid may contact this person if there are any issues or questions regarding the submitted information.

Shipping Info

Trustgrid will send shipping information to this email address.

is the shipping address the same as the deployment address?

Address*

Summary

Please, make sure that the information entered is correct before submitting it. Do also save a snapshot of your data for future reference.
{all_fields}

back to top

Quick Links

  • Resources
  • Support
  • Technology Partners
  • Request Free Trial
  • FAQ

Products

  • Connect
  • EdgeCompute
  • Remote Access

Contact

888.308.8995

info@trustgrid.io

12710 Research Blvd
Suite 365
Austin, TX 78759

©2023 Trustgrid, Inc. | Trustgrid™ is a trademark of Trustgrid Inc. All Rights Reserved. | Privacy | Website Design by MODintelechy