Domains
Connect existing domains, document ownership, plan subdomains, renewals, transfers, and recovery contacts.
Digital Infrastructure for the Verve N Veda Network
A calm, professional infrastructure workspace for mapping domains, preparing DNS, organizing publishing, planning future mail identities, documenting security, and preserving portable records for member-owned digital spaces.
This local-first version creates infrastructure plans and DNS record drafts on the current device. It does not register domains, alter nameservers, deliver mail, deploy servers, or store provider credentials.
Twelve Infrastructure Halls
Each hall begins as an honest planning interface and is prepared for later connection to authenticated production services without changing Bunya’s public identity.
Connect existing domains, document ownership, plan subdomains, renewals, transfers, and recovery contacts.
Draft A, AAAA, CNAME, MX, TXT, SPF, DKIM, DMARC, SRV, and CAA records before provider entry.
Prepare member addresses, aliases, groups, quotas, recovery methods, and future mail policies.
Open E=Ven MailLink people, organizations, domains, mailboxes, roles, devices, permissions, and recovery methods.
Connect landing pages, portals, portfolios, organizations, and public-service destinations.
Open SIte BuilderPlan private files, object storage, media, quotas, signed access, retention, and synchronized workspaces.
Plan repository connections, build pipelines, releases, environments, rollbacks, and application publishing.
Prepare caching, global asset delivery, regional routing, invalidation, and performance policies.
Document manifests, service workers, icons, installability, offline behavior, and application updates.
Track uptime, DNS health, certificates, storage, deployments, incidents, and service status.
Plan encrypted backups, restore points, retention schedules, recovery testing, and export archives.
Track HTTPS, access roles, logs, alerts, credentials, renewals, and administrative safeguards.
Bunya Infrastructure Workspace
Create multiple local plans, attach DNS record drafts and readiness checklists, then export an individual plan or the complete Bunya workspace as portable JSON.
Do not place passwords, API tokens, private keys, recovery codes, or provider secrets in this browser workspace.
Bunya reads same-origin local records from the rebuilt applications. Detection confirms that browser data exists; it does not prove a remote account, mailbox, deployment, public registration, or cross-device synchronization.
No completed HOLLO enrollment detected.
Turn detected application records into editable Bunya plans without copying passwords or provider secrets.
Draft records for the selected plan. Values are explanatory workspace data only; provider-generated values must be copied from the actual hosting, DNS, mail, or verification service.
| Type | Name | Value | Priority | TTL | Action |
|---|
Track the selected plan’s preparation without implying that any provider action has been completed automatically.
Bunya’s public interface and local planning workspace are active. Production infrastructure remains staged by service.
333 Network Suite
Bunya remains the planning and infrastructure layer while each application retains its own purpose, permissions, local data, and honest production boundary.
Trusted contacts, private message threads, and consent-based call invitations.
Open HOLLOPrivate meeting rooms, invitations, room chat, notes, and media previews.
Open KANSEELocal correspondence workspace prepared for future authenticated delivery.
Open E=Ven MailCreative posts, artists, groups, events, comments, reels, and shared inspiration.
Open BazaarBrowser-based website and application building with local project portability.
Open SIteThe shared gateway, application directory, established route finder, and installable PWA shell.
Open GatewayDNS & Mail Identity Guide
These cards explain common record purposes. Real values must come from the actual hosting, DNS, mail, verification, security, or registrar service.
APoints a hostname to an IPv4 destination supplied by the hosting service.
AAAAPoints a hostname to an IPv6 destination where the connected service supports it.
CNAMEConnects a subdomain to another hostname, often for hosted websites or applications.
MXDirects incoming email toward authorized E=Ven Mail or external mail servers.
TXTStores ownership checks, service verification, policies, and other text values.
SPFDeclares which systems may send email on behalf of a domain.
DKIMPublishes a public key used to validate signatures on outgoing mail.
DMARCDefines handling for failed identity checks and where aggregate reports are sent.
Bunya Stewardship Principles
Domain ownership, renewal responsibility, transfer rights, billing, and administrative authority must be documented clearly.
Registrar tokens, DNS keys, DKIM private keys, mailbox credentials, and administrator secrets never belong in public HTML or local notes.
A planning interface is not represented as a registrar, nameserver, mail host, cloud provider, or deployment service until those systems exist.
Members should be able to export plans, move domains, recover data, and change providers without losing access to their identity.
Authentication, permissions, logging, backups, recovery, monitoring, and incident response come before public provisioning.
Bunya, E=Ven Mail, 333 Identity, HOLLO, KANSEE, Bazaar, SIte, and public websites share a network while preserving separate permissions.