This page lists what is actually available today for someone evaluating, planning, or running an OasisCore activation, and is explicit about what does not exist yet. Most OasisCore material is currently reached through DigiFX rather than self-served.
01Support and contact
The route into help for every OasisCore topic in this knowledgebase is the DigiFX contact channel at digifx.com/contact. Each card in the OasisCore section of the knowledgebase resolves there, and the section's own banner points to the same place for bespoke technical questions.
That is a deliberate arrangement rather than a missing feature. OasisCore activations are production engagements involving site selection, narrative design, and reward planning, so the useful first exchange is a conversation about the objective, not a documentation search. Come with the location or locations, the run window, the audience size you expect, and what a successful outcome looks like, and the scoping conversation is short.
02Knowledgebase coverage
The OasisCore section of the DigiFX knowledgebase is organised into nine topics, covering the value proposition, market strategy, business summary, system components, media hardware, company prototypes, experience campaign, product resources, and future projects. The System Components and Experience Campaign pages carry the most technical detail and are the right starting point for a technical evaluator; Value Proposition and Market Strategy are the right starting point for a commercial one.
The wider DigiFX knowledgebase places OasisCore alongside sibling sections for the Agency Platform, eXperience Over Media, hardware devices, software integration, and media production. Where an OasisCore activation touches production or hardware work, those sections are the neighbouring reference.
03Platform documentation
Oasis is documented internally as an execution platform within the wider DigiFX and DragonSource estate, with a public-facing domain recorded as relicoasis.com. Internal material covers its architecture, its integration surface with the rest of the estate, its service and cost model, and its access and anti-cheat design. Those documents inform this knowledgebase but are not themselves published.
There is currently no public API reference, integration guide, or developer portal for Oasis. Internal notes describe the integration routes that exist between Oasis and the rest of the estate, but these are internal service interfaces, not a published third-party API. Anyone planning to build against Oasis should treat integration as a scoped conversation rather than a documented self-service path.
04What to ask for
If you are evaluating OasisCore, the questions worth raising up front are the ones this knowledgebase cannot yet answer: current availability and lead time, pricing and packaging, supported participant devices, what reporting you receive during and after a run, and who carries responsibility for site permissions at each location. Each of those is a real decision rather than an oversight, and each is better settled before a proposal than after.