Connect the services your application needs.
Repositories, domains, databases, and object storage have distinct responsibilities in a PHP deployment.
Connections with a clear purpose
An integration should say what it does, which permission it requires, and whether it is available. Orisite keeps provider credentials on the server and separates metadata from execution.
Connections with an owner and a purpose.
Separate build inputs, persistent services, and domain operations.
Code and build inputs
A source provider supplies the revision. Repository access and webhook verification are separate from permission to deploy to production.
Application data
Database connections and storage credentials belong to an environment. A code release does not provision or back up a database by itself.
Domain and traffic lifecycle
Dynadot is the selected registrar. Registration, renewal, transfer, nameservers, domain ownership, DNS routing, and TLS are distinct operations.
Domain registration is a provider transaction
A domain search is not a reservation. Before registration, the customer needs an authoritative availability result, a price and term, registrant details, and the applicable registrar conditions. A successful provider result must be reconciled with the order before the panel marks a domain as registered.
Renewals, transfers, and nameserver changes require their own workflow and failure handling. Live Dynadot transactions are not active yet; the website must not imply that a request has purchased or renewed a domain.
Bring your PHP application, choose the runtime it needs, and keep releases, domains, and operations together in your Orisite panel.
